Netdev List
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@monatomic.org>
To: Linux Kernel List <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Cc: Nick Piggin <nickpiggin@yahoo.com.au>
Subject: workaround large MTU and N-order allocation failures
Date: Sun, 18 Sep 2005 17:35:26 +0300	[thread overview]
Message-ID: <20050918143526.GA24181@localdomain> (raw)

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.

Thanks,

-- 
Dan Aloni
da-x@monatomic.org, da-x@colinux.org, da-x@gmx.net

             reply	other threads:[~2005-09-18 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 14:35 Dan Aloni [this message]
2005-09-18 23:08 ` workaround large MTU and N-order allocation failures 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
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=20050918143526.GA24181@localdomain \
    --to=da-x@monatomic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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