netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Iatrou <m.iatrou@freemail.gr>
To: e1000-devel@lists.sourceforge.net
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Ming Zhang <mingz@ele.uri.edu>,
	iet-dev <iscsitarget-devel@lists.sourceforge.net>,
	netdev@vger.kernel.org
Subject: Re: [E1000-devel] Page Allocation Failure with e1000 using jumbo frame
Date: Sat, 20 Aug 2005 04:43:40 +0300	[thread overview]
Message-ID: <200508200443.40251.m.iatrou@freemail.gr> (raw)
In-Reply-To: <Pine.WNT.4.63.0508190940210.3796@jbrandeb-desk.amr.corp.intel.com>

When the date was Friday 19 August 2005 19:51, Jesse Brandeburg wrote:

> included netdev...
>
> On Wed, 17 Aug 2005, Ming Zhang wrote:
> > Hi folks
> >
> > We ran into this problem when running jumbo frame with iscsi over e1000.
> > the MTU1500 is fine while jumbo frame can stably reproduce this error.
> >
> > when meet this error, as reported in iet list, the box still has >600MB
> > ram free. also the slab is not heavily used.
> >
> > any idea on this?
>
> So, what we do know is that your kernel memory manager is (for whatever
> unknown reason) having trouble finding contiguous 2^3 pages (32kB) chunks
> of memory.  This occurs because we need to give our hardware 16kB
> contiguous (currently, we actually have a patch for this in internal
> testing) which means that when we do dev_alloc_skb, it allocates 16kB + 16
> bytes reserve, plus 2 bytes NET_IP_ALIGN, which takes us into the 32kB
> slab (power of two roundup)

I don't get it: For MTU = 9000, you already have to allocate 2^3 pages, but 
testing shows that the problem only occurs for MTU > 3*PAGE_SIZE

http://members.hellug.gr/iatrou/plain_ip_mtu.png

(reference to previous discussion)
http://sourceforge.net/mailarchive/forum.php?forum_id=12401&max_rows=25&style=ultimate&viewmonth=200505

-- 
 Michael Iatrou
 Electrical and Computer Engineering Dept.
 University of Patras, Greece


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

      parent reply	other threads:[~2005-08-20  1:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1124326404.5546.215.camel@localhost.localdomain>
2005-08-19 16:51 ` [E1000-devel] Page Allocation Failure with e1000 using jumbo frame Jesse Brandeburg
2005-08-19 17:01   ` Ming Zhang
2005-08-19 17:33     ` Page Allocation Failure with e1000 using jumboframe Jesse Brandeburg
2005-08-19 17:42       ` [E1000-devel] " Andi Kleen
2005-08-19 17:51         ` Jesse Brandeburg
2005-08-19 18:01           ` Andi Kleen
2005-08-19 19:07             ` Ming Zhang
2005-08-19 21:10             ` Jesse Brandeburg
2005-08-19 17:52       ` Ming Zhang
2005-08-20  1:46       ` Michael Iatrou
2005-08-19 17:02   ` Page Allocation Failure with e1000 using jumbo frame Andi Kleen
2005-08-19 18:10     ` [E1000-devel] " Martin Josefsson
2005-08-19 17:03   ` Nivedita Singhvi
2005-08-20  1:43   ` Michael Iatrou [this message]

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=200508200443.40251.m.iatrou@freemail.gr \
    --to=m.iatrou@freemail.gr \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=iscsitarget-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=mingz@ele.uri.edu \
    --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;
as well as URLs for NNTP newsgroup(s).