From owner-freebsd-current@FreeBSD.ORG Sun May 30 08:11:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1300D16A4CE for ; Sun, 30 May 2004 08:11:20 -0700 (PDT) Received: from oasis.uptsoft.com (oasis.uptsoft.com [217.20.165.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2C0643D54 for ; Sun, 30 May 2004 08:11:18 -0700 (PDT) (envelope-from devnull@oasis.uptsoft.com) Received: (from devnull@localhost) by oasis.uptsoft.com (8.11.6/linuxconf) id i4UFBHN28773 for freebsd-current@freebsd.org; Sun, 30 May 2004 18:11:17 +0300 Date: Sun, 30 May 2004 18:11:17 +0300 From: Sergey Lyubka To: freebsd-current@freebsd.org Message-ID: <20040530181117.A28616@oasis.uptsoft.com> Mail-Followup-To: freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from don@sandvine.com on Sun, May 30, 2004 at 10:30:30AM -0400 X-OS: FreeBSD 4.5-STABLE Subject: Re: crash when bpf is used heavily X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 May 2004 15:11:20 -0000 > The problem the original post has, although on the > surface kind of nasty (easily able to panic from user > space), can be easily worked around by creating > less bpf devices (/dev/bpf0, ... create only 4 of > them) and appropriately resizing KVA. If I recall, > he had also increased quite dramatically the bpf > buffer size. > > --don /dev is devfs-mounted