From: Al Boldi <a1426z@gawab.com>
To: netdev@vger.kernel.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: workaround large MTU and N-order allocation failures
Date: Mon, 19 Sep 2005 16:38:15 +0300 [thread overview]
Message-ID: <200509191638.15506.a1426z@gawab.com> (raw)
In-Reply-To: <1127111462.5272.7.camel@npiggin-nld.site>
Nick Piggin wrote:
> On Sun, 2005-09-18 at 17:35 +0300, Dan Aloni wrote:
> > Hello,
> >
> > Is there currently a workaround available for handling large MTU
> > (larger than 1 page, even 2-order) in the Linux network stack?
> >
> > The problem with large MTU is external memory fragmentation in
> > the buddy system following high workload, causing alloc_skb() to
> > fail.
> >
> > I'm interested in patches for both 2.4 and 2.6 kernels.
>
> Yes there is currently a workaround. That is to keep increasing
> /proc/sys/vm/min_free_kbytes until your allocation failures stop.
How do you do it in 2.4?
--
Al
next prev parent reply other threads:[~2005-09-19 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 14:35 Dan Aloni
2005-09-18 23:08 ` Francois Romieu
2005-09-19 7:13 ` Dan Aloni
2005-09-19 17:25 ` Ganesh Venkatesan
2005-09-20 14:25 ` Dan Aloni
2005-09-19 6:31 ` Nick Piggin
2005-09-19 13:38 ` Al Boldi [this message]
2005-09-20 14:34 ` Dan Aloni
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=200509191638.15506.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®