From owner-cvs-src@FreeBSD.ORG Tue Jun 7 09:26:50 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 27BAB16A41C; Tue, 7 Jun 2005 09:26:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from pasmtp.tele.dk (pasmtp.tele.dk [193.162.159.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E9043D1D; Tue, 7 Jun 2005 09:26:49 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x535c0e2a.sgnxx1.adsl-dhcp.tele.dk [83.92.14.42]) by pasmtp.tele.dk (Postfix) with ESMTP id 377691EC375; Tue, 7 Jun 2005 11:26:45 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.3/8.13.3) with ESMTP id j579Qe3t097027; Tue, 7 Jun 2005 11:26:41 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 07 Jun 2005 19:24:14 +1000." <20050607092414.GC39114@cirb503493.alcatel.com.au> Date: Tue, 07 Jun 2005 11:26:40 +0200 Message-ID: <97026.1118136400@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: cvs-src@freebsd.org, src-committers@freebsd.org, "Christian S.J. Peron" , 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:26:50 -0000 In message <20050607092414.GC39114@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@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.