From owner-freebsd-net@FreeBSD.ORG Sun Sep 5 23:01:04 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1824216A4CE; Sun, 5 Sep 2004 23:01:03 +0000 (GMT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 387CF43D1F; Sun, 5 Sep 2004 23:01:03 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id i85N11ip082369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Sep 2004 03:01:02 +0400 (MSD) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id i85N10r6082352; Mon, 6 Sep 2004 03:01:00 +0400 (MSD) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 6 Sep 2004 03:01:00 +0400 From: Gleb Smirnoff To: Luigi Rizzo Message-ID: <20040905230100.GA82214@cell.sick.ru> References: <20040905205249.GA81337@cell.sick.ru> <20040905142036.A23213@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20040905142036.A23213@xorpc.icir.org> User-Agent: Mutt/1.5.6i cc: hackers@freebsd.org cc: net@freebsd.org Subject: Re: bridge callbacks in if_ed.c? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2004 23:01:04 -0000 On Sun, Sep 05, 2004 at 02:20:36PM -0700, Luigi Rizzo wrote: L> there are performance reasons to do this way -- grabbing L> the entire packet is expensive because it is done via programmed L> I/O, so the current code only grabs the header, does the L> filtering, and grabs the rest of the packet only if L> needed. Well, thinking deeply I have to admit that percentage of dropped packets can be high under normal operation. If we are connected to non-swithced network (e.g. coax) percentage of dropped packets is high... But my position didn't change, I absolutely agree with Andre. We can't keep this hack for the sake of very old and rare hardware. L> I'd rather not apply the patch unless you can show that L> the current code leads to incorrect behaviour. I suspect that packets dropped by bridge_in() called from if_ed will not be captured by bpf(4). This is incorrect. System administrators expect bpf(4) to be at the lowest possible layer, thinking "if packet came on wire - tcpdump must show it". -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE