From owner-freebsd-current Sat Apr 25 13:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16160 for freebsd-current-outgoing; Sat, 25 Apr 1998 13:56:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16154 for ; Sat, 25 Apr 1998 13:56:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA12181; Sat, 25 Apr 1998 15:56:16 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199804252056.PAA12181@dyson.iquest.net> Subject: Re: Bandwidth throttling etc. In-Reply-To: <908.893476488@cloud.rain.com> from Bill Trost at "Apr 24, 98 08:54:48 pm" To: trost@cloud.rain.com (Bill Trost) Date: Sat, 25 Apr 1998 15:56:16 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Garrett Wollman writes: > What you Really Want is for each interface to manage its own > allocations. When you want to send a packet, you ask the interface > for a buffer, and it gives you one of an appropriate size and shape > that it knows how to transmit efficiently..... > > A lot of the work is not actually difficult, just tedious.... > > Before anyone spends oodles of time doing this sort of work, has anyone > taken the radical (-: step of actually profiling the current network > stack(s) to see where the time is being eaten? Improving the memory > access behavior may not gain very much, especially if the performance > hits occur in, say, the IP checksum computation (as a random example). > > Maybe someone has already looked at this and this is just rehashing old > news, but it just struck me that some hard data would be an important > guide. > AFAIK, and I am NOT a networking export, we need to improve the sockets layer as much as the lower level networking code. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message