From owner-freebsd-current@FreeBSD.ORG Sun May 30 07:30:37 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 AF9C916A4CE for ; Sun, 30 May 2004 07:30:37 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44E2A43D31 for ; Sun, 30 May 2004 07:30:37 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72) id ; Sun, 30 May 2004 10:30:32 -0400 Message-ID: From: Don Bowman To: 'Kris Kennaway' , freebsd-current@freebsd.org Date: Sun, 30 May 2004 10:30:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" 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 14:30:37 -0000 From: Kris Kennaway [mailto:kris@obsecurity.org] > On Sat, May 29, 2004 at 04:03:45PM +0300, Sergey Lyubka wrote: > > > put M_NOWAIT in bpf_allocbufs(). > > Got page fault now. > > panic: kmem_malloc(4098) too small > > That means "You have run out of KVA" and need to reduce the workload, > or retune the kernel memory allocations. 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