From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.1 network (socket) performance
Date: Fri, 23 Feb 2001 10:58:28 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.95.1010223104549.2101B-100000@chaos.analogic.com> (raw)
In-Reply-To: <3A966FF1.2C9E5641@colorfullife.com>
Hello,
The problem with awful socket performance on 2.4.1 has been discovered
and fixed by Manfred Spraul. Here is some info, and his patch:
On Fri, 23 Feb 2001, Manfred Spraul wrote:
> Could you post your results to linux-kernel?
> My mail from this morning wasn't accurate enough, you patched the wrong
> line. Sorry.
Yep. The patch you sent was a little broken. I tried to fix it, but
ended up pathing the wrong line.
>
> I've attached the 2 patches that should cure your problems.
> patch-new is integrated into the -ac series, and it's a bugfix - simple
> unix socket sends eat into memory reserved for atomic allocs.
> patch-new2 is the other variant, it just deletes the fallback system.
--- linux/net/core/sock.c Fri Dec 29 23:07:24 2000
+++ linux/net/core/sock.c.new Fri Feb 23 15:02:46 2001
@@ -777,7 +777,7 @@
/* The buffer get won't block, or use the atomic queue.
* It does produce annoying no free page messages still.
*/
- skb = alloc_skb(size, GFP_BUFFER);
+ skb = alloc_skb(size, sk->allocation & (~__GFP_WAIT));
if (skb)
break;
try_size = fallback;
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
next parent reply other threads:[~2001-02-23 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A966FF1.2C9E5641@colorfullife.com>
2001-02-23 15:58 ` Richard B. Johnson [this message]
2001-02-26 23:53 ` Linux 2.4.1 network (socket) performance David S. Miller
2001-02-27 11:59 ` Alan Cox
2001-02-22 16:11 Richard B. Johnson
2000-01-01 1:38 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.95.1010223104549.2101B-100000@chaos.analogic.com \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).