From owner-freebsd-hackers Fri May 17 20:41:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA19571 for hackers-outgoing; Fri, 17 May 1996 20:41:47 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA19552 for ; Fri, 17 May 1996 20:41:40 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id VAA00514; Fri, 17 May 1996 21:39:08 -0600 Date: Fri, 17 May 1996 21:39:08 -0600 From: Nate Williams Message-Id: <199605180339.VAA00514@rocky.sri.MT.net> To: Michael Smith Cc: nate@sri.MT.net (Nate Williams), hackers@FreeBSD.org Subject: Re: Note from Usenet In-Reply-To: <199605180220.LAA15853@genesis.atrad.adelaide.edu.au> References: <199605171652.KAA27616@rocky.sri.MT.net> <199605180220.LAA15853@genesis.atrad.adelaide.edu.au> Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Gleaned froma Linux mailing list. > > > > > About a week ago, Alan Cox commented that the networking code in 1.3.xx > > > wasn't up to coping with the type of load that a WWW server would > > > experience, and that 1.2.xx was a better choice for that application. > > > > Apparently Linux 1.3 with the re-written TCP/IP code still isn't up to > > the task. > > Sheesh. What it must have cost him to say _that_. Bit of a pity, really. And he's the author of the new code, so what he says is most definitely an unbiased opinion. I saw some other notes on other articles that it appears to be a problem with the new kernel malloc routines. Apparently the real-time extensions are getting in the way of the kernel being able to service it's own internal memory requests for things like network buffers and such. Nate