From owner-freebsd-current Sat Apr 25 14:02:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17273 for freebsd-current-outgoing; Sat, 25 Apr 1998 14:02:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17241 for ; Sat, 25 Apr 1998 14:02:32 -0700 (PDT) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id QAA18391; Sat, 25 Apr 1998 16:02:26 -0500 (CDT) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id QAA22916; Sat, 25 Apr 1998 16:02:26 -0500 (CDT) Message-ID: <19980425160226.17154@mcs.net> Date: Sat, 25 Apr 1998 16:02:26 -0500 From: Karl Denninger To: "John S. Dyson" Cc: Bill Trost , current@FreeBSD.ORG Subject: Re: Bandwidth throttling etc. References: <908.893476488@cloud.rain.com> <199804252056.PAA12181@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: <199804252056.PAA12181@dyson.iquest.net>; from John S. Dyson on Sat, Apr 25, 1998 at 03:56:16PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 25, 1998 at 03:56:16PM -0500, John S. Dyson wrote: > > 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 Where do you believe there are deficiencies in the socket layer at present? I *HAVE* done some work in there (for our own proprietary stuff) and might be able to make some improvements. I haven't noticed any particularly "evil" behavior of late, and as such haven't spent time on this. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message