Evgeniy Polyakov wrote:
> On Thu, Aug 03, 2006 at 08:09:07PM +0200, Arnd Hannemann ([EMAIL PROTECTED])
> wrote:
>> Evgeniy Polyakov schrieb:
>>> On Thu, Aug 03, 2006 at 07:16:31PM +0400, Evgeniy Polyakov ([EMAIL
>>> PROTECTED]) wrote:
>>>>>> th
Evgeniy Polyakov schrieb:
> On Thu, Aug 03, 2006 at 07:16:31PM +0400, Evgeniy Polyakov ([EMAIL
> PROTECTED]) wrote:
then skb_alloc adds a little
(sizeof(struct skb_shared_info)) at the end, and this ends up
in 32k request just for 9k jumbo frame.
>>> Strange, why this skb_shared_inf
arrives the hardware will accept it regardless of
the 2k MTU and will split it into 3x 4k rx buffers?
Does the current driver work in this way? That would be great.
Perhaps then one should change the driver in a way that the MTU can
changed independently of the buffer size?
> - Chris
> -
Thanks,
Arnd Hannemann.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
ign then add)?
>
> It can be.
> Could attached (completely untested) patch help?
I will try this in a minute. However is there any way to see which
allocation e1000 does without triggering allocation failures? ;-)
Thanks,
Arnd Hannemann
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Benjamin LaHaise schrieb:
> On Thu, Aug 03, 2006 at 03:48:39PM +0200, Arnd Hannemann wrote:
>> However the box is a VIA Epia MII12000 with 1 GB of Ram and 1 GB of swap
>> enabled, so there should be plenty of memory available. HIGHMEM support
>> is off. The e1000 nic seems to
Hi,
Evgeniy Polyakov wrote:
> On Thu, Aug 03, 2006 at 03:48:39PM +0200, Arnd Hannemann ([EMAIL PROTECTED])
> wrote:
>> Hi,
>>
>> im running vanilla 2.6.17.6 and if i try to set the mtu of my e1000 nic
>> to 9000 bytes, page allocation failures occur (see below).
k+0x2/0x10 dput+0x1e/0x120
> prune_dcache+0xe6/0xf0 shrink_dcache_memory+0x14/0x40
> shrink_slab+0x16f/0x1d0 throttle_vm_writeout+0x26/0x70
> balance_pgdat+0x2e3/0x3b0 kswapd+0xf3/0x110
> autoremove_wake_function+0x0/0x50
> autoremove_wake_function+0x0/0x50
> kswapd+
