From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evgeniy Polyakov Subject: Re: problems with e1000 and jumboframes Date: Thu, 3 Aug 2006 17:59:25 +0400 Message-ID: <20060803135925.GA28348@2ka.mipt.ru> References: <44D1FEB7.2050703@arndnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: Received: from relay.2ka.mipt.ru ([194.85.82.65]:64152 "EHLO 2ka.mipt.ru") by vger.kernel.org with ESMTP id S932466AbWHCN7h (ORCPT ); Thu, 3 Aug 2006 09:59:37 -0400 To: Arnd Hannemann Content-Disposition: inline In-Reply-To: <44D1FEB7.2050703@arndnet.de> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Aug 03, 2006 at 03:48:39PM +0200, Arnd Hannemann (arnd@arndnet.de) 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). > > 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 be an 82540EM, which to my knowledge > should support jumboframes. But it does not support splitting them into page sized chunks, so it requires the whole jumbo frame allocation in one contiguous chunk, 9k will be transferred into 16k allocation (order 3), since SLAB uses power-of-2 allocation. > However I can't always reproduce this on a freshly booted system, so > someone else may be the culprit and leaking pages? You will almost 100% reproduce it after "find / > /dev/null". > Any ideas how to debug this? It can not be debugged - you have cought a memory fragmentation problem, which is quite common. > > kswapd0: page allocation failure. order:3, mode:0x20 e1000 tries to allocate 3-order pages atomically? Well, that's wrong. > Thanks, > Arnd Hannemann -- Evgeniy Polyakov