From owner-cvs-src@FreeBSD.ORG Tue Jun 7 09:24:18 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DD1716A41C; Tue, 7 Jun 2005 09:24:18 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB91143D1F; Tue, 7 Jun 2005 09:24:17 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) by mail03.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j579OFlb031609 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 7 Jun 2005 19:24:15 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j579OERx040795; Tue, 7 Jun 2005 19:24:14 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j579OEa3040794; Tue, 7 Jun 2005 19:24:14 +1000 (EST) (envelope-from pjeremy) Date: Tue, 7 Jun 2005 19:24:14 +1000 From: Peter Jeremy To: "Christian S.J. Peron" Message-ID: <20050607092414.GC39114@cirb503493.alcatel.com.au> References: <200506062219.j56MJxkw029530@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200506062219.j56MJxkw029530@repoman.freebsd.org> User-Agent: Mutt/1.4.2i Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/net bpf.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 09:24:18 -0000 On Mon, 2005-Jun-06 22:19:59 +0000, Christian S.J. Peron wrote: > Change the maximum bpf program instruction limitation from being hard- > coded at 512 (BPF_MAXINSNS) to being tunable. This is useful for users > who wish to use complex or large bpf programs when filtering traffic. > For now we will default it to BPF_MAXINSNS. I have tested bpf programs > with well over 21,000 instructions without any problems. If people are using really large BPF programs, is there a benefit in moving from bytecode to machine code? -- Peter Jeremy