From owner-freebsd-current@FreeBSD.ORG Mon Jun 12 20:21:10 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 BA52D16A418; Mon, 12 Jun 2006 20:21:10 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC92743D45; Mon, 12 Jun 2006 20:21:08 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k5CKL3Wm061811; Mon, 12 Jun 2006 16:21:03 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Mon, 12 Jun 2006 16:20:42 -0400 User-Agent: KMail/1.6.2 References: <20060612185751.GB1226@roadrunner.aventurien.local> In-Reply-To: <20060612185751.GB1226@roadrunner.aventurien.local> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200606121620.44136.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1534/Mon Jun 12 08:30:53 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Vadim Goncharov , freebsd-isp@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] ng_tag - new netgraph node, please test (L7 filtering possibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 12 Jun 2006 20:21:10 -0000 On Monday 12 June 2006 02:57 pm, Ulrich Spoerlein wrote: > Vadim Goncharov wrote: > > I hope that my explanation was helpful enough to understand :) > > Also, if you will be using 7.0, include BPF_JITTER in your kernel > > config as this will enable native code-compiling for bpf and > > ng_bpf - this will speed things up. > > Am I the only one, that thinks BPF_JITTER is a stupid name? It > suggest you add or enable jitter for the packet flow. No one wants > jitter! It sucks. Why isn't it called simply BPF_JIT? Everyone > knows what JIT stands for, JITTER on the other hand is to be > avoided. I am the guilty one and I hate the name myself. :-) This feature was imported from WinPcap: http://www.winpcap.org/docs/docs31/html/group__NPF__code.html#ga33 I didn't want another name for the same thing. Jung-uk Kim