cvs commit: src/sys/net bpf.c

[Poul-Henning Kamp]

In message <20050607092414.GC39114 at cirb503493.alcatel.com.au>, Peter Jeremy writes:
>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?

I'm sure there would be, but we wouldn't be compatible with everybody
else if we did so.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.