From: "David S. Miller" <davem@redhat.com>
To: Chris Leech <chris.leech@gmail.com>
Cc: shane@hathawaymix.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000 rx buffer allocation
Date: Fri, 27 Aug 2004 12:36:29 -0700 [thread overview]
Message-ID: <20040827123629.4b9c6a55.davem@redhat.com> (raw)
In-Reply-To: <41b516cb04082711363a009dbc@mail.gmail.com>
On Fri, 27 Aug 2004 11:36:36 -0700
Chris Leech <chris.leech@gmail.com> wrote:
> A better approach for improving jumbo frame allocations might be to
> use multiple smaller buffers for each receive, something the PRO/1000
> hardware can do but the e1000 driver has never taken advantage of.
>
> Dave, you mentioned the possibility of drivers doing that in a
> conversation with Harald about handling fragmented packets
> (http://marc.theaimsgroup.com/?l=linux-netdev&m=109293677816177&w=2)
> What would be the more correct approach to this? Putting all receive
> data into page allocations and filling out the frags array, or
> chaining together small skbs using the frag_list?
Yes, you can use multiple buffers for receive packet receive
and the network stack will handle it just fine. I would recommend
using 256 bytes for the skb->data area and put the rest in page
frags.
next prev parent reply other threads:[~2004-08-27 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 23:35 [PATCH] e1000 rx buffer allocation shane
2004-08-27 1:18 ` David S. Miller
2004-08-27 1:18 ` David S. Miller
2004-08-27 18:36 ` Chris Leech
2004-08-27 19:36 ` David S. Miller [this message]
2004-08-28 2:27 ` Shane Hathaway
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=20040827123629.4b9c6a55.davem@redhat.com \
--to=davem@redhat.com \
--cc=chris.leech@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shane@hathawaymix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.