Date: Tue, 7 Jun 2005 19:24:14 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: "Christian S.J. Peron" <csjp@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/net bpf.c Message-ID: <20050607092414.GC39114@cirb503493.alcatel.com.au> In-Reply-To: <200506062219.j56MJxkw029530@repoman.freebsd.org> References: <200506062219.j56MJxkw029530@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050607092414.GC39114>