From: Andi Kleen <ak@suse.de>
To: Mark Hayden <mark@northforknet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux networking and disk IO issues
Date: 13 Jun 2001 12:36:06 +0200 [thread overview]
Message-ID: <oupelsoll9l.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <3B1BB85B.360CE0F6@northforknet.com.suse.lists.linux.kernel>
In-Reply-To: Mark Hayden's message of "4 Jun 2001 20:17:03 +0200"
[this time with l-k cc]
Mark Hayden <mark@northforknet.com> writes:
> * The Linux networking stack requires all skbuff buffers to be
> contiguous. As far as I can tell, this makes it impossible to
> write high-bandwidth UDP applications on Linux. For instance, the
> kernel will drop a fragmented 8KB message if it cannot allocate 8KB
> of contiguous memory to reassemble it into. I have found that it
> is relatively easy to enter regimes where this can cause massive
> packet loss.
2.4.4+ supports fragmented packets and packet lists.
You're probably seeing the 8K allocation problem for incoming packets which need to be
allocated by the driver on interrupt time with GFP_ATOMIC. GFP_ATOMIC memory is limited.
The 2.4 VM unfortunately has no way to keep more GFP_ATOMIC free ATM and tune for heavy
interrupt load (2.2 allowed this by increasing the freepages sysctl). Hopefully this VM bug
will be fixed in the not too far future.
A workaround in the driver would be to use the 2.4.4 fragmented buffers
(of course you'll still run into GFP_ATOMIC limits without manual tuning)
or allocate RX memory from a thread with GFP_KERNEL.
-Andi
next parent reply other threads:[~2001-06-13 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B1BB85B.360CE0F6@northforknet.com.suse.lists.linux.kernel>
2001-06-13 10:36 ` Andi Kleen [this message]
2001-06-04 16:33 Linux networking and disk IO issues Mark Hayden
2001-06-04 20:02 ` Alan Cox
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=oupelsoll9l.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@northforknet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.