From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 14 17:48:04 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13D5316A4CE for ; Mon, 14 Jun 2004 17:48:04 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCFA143D1D for ; Mon, 14 Jun 2004 17:48:03 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 80FBA6520F; Mon, 14 Jun 2004 18:47:51 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 66619-02-12; Mon, 14 Jun 2004 18:47:51 +0100 (BST) Received: from empiric.dek.spc.org (82-147-17-88.dsl.uk.rapidplay.com [82.147.17.88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E7131651F4; Mon, 14 Jun 2004 18:47:50 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id C5B786119; Mon, 14 Jun 2004 18:47:49 +0100 (BST) Date: Mon, 14 Jun 2004 18:47:49 +0100 From: Bruce M Simpson To: Ed Maste Message-ID: <20040614174749.GF14722@empiric.dek.spc.org> Mail-Followup-To: Ed Maste , 'Sergey Lyubka' , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-hackers@freebsd.org cc: 'Sergey Lyubka' Subject: Re: memory mapped packet capturing - bpf replacement ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2004 17:48:04 -0000 On Mon, Jun 14, 2004 at 08:38:57AM -0400, Ed Maste wrote: > Hello Sergey. I haven't looked at your code, but I'll provide > some comments, having implemented a mmaped ringbuffer BPF > replacement myself. We've had some prior interest in this. Do you have patches? If so, I'd be more than happy to look at them. Linux has something similar, but when I looked at the mechanism involved, I was loathe to adopt the same logic because the buffer(s) involved were allocated from userland and then mapped accordingly; we generally can't afford to take a page fault in that path, for mutex related reasons. Regards, BMS