workaround large MTU and N-order allocation failures

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
[email protected], [email protected], [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: workaround large MTU and N-order allocation failures
  - From: Nick Piggin <[email protected]>
- Re: workaround large MTU and N-order allocation failures
  - From: Francois Romieu <[email protected]>

Prev by Date: [PATCH 02/12] HPPFS: don't check sb->s_op in is_pid()
Next by Date: Re: p = kmalloc(sizeof(*p), )
Previous by thread: [PATCH 02/12] HPPFS: don't check sb->s_op in is_pid()
Next by thread: Re: workaround large MTU and N-order allocation failures
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]