From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Andi Kleen <ak@suse.de>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Ming Zhang <mingz@ele.uri.edu>,
E1000 <e1000-devel@lists.sourceforge.net>,
iet-dev <iscsitarget-devel@lists.sourceforge.net>,
netdev@vger.kernel.org
Subject: Re: [E1000-devel] Page Allocation Failure with e1000 using jumbo frame
Date: Fri, 19 Aug 2005 20:10:56 +0200 [thread overview]
Message-ID: <1124475056.23996.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20050819170248.GH3953@verdi.suse.de>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Fri, 2005-08-19 at 19:02 +0200, Andi Kleen wrote:
> > I guess we need to approach the memory manager guys and ask them why the
> > current kernels are having so much trouble getting contiguous memory.
>
> Because memory fragments.
>
> The only long term reliable way is to not allocate buffers > PAGE_SIZE.
> The stack supports paged skbs for that.
And the e1000 supports receiving/transmitting packets containing several
buffers according to the SDM, it just uses more descriptors in the rx/tx
rings.
Maybe it should allocate PAGE_SIZE large buffers, a 9kB packet would
then use 3 such buffers.
And it of course means more and smaller DMA transfers than when using
larger buffers.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-19 18:10 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 ` Martin Josefsson [this message]
2005-08-19 17:03 ` Nivedita Singhvi
2005-08-20 1:43 ` [E1000-devel] " Michael Iatrou
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=1124475056.23996.15.camel@localhost.localdomain \
--to=gandalf@wlug.westbo.se \
--cc=ak@suse.de \
--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).