From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: mekaviraj@gmail.com, netdev@vger.kernel.org
Subject: Re: NETIF_F_FRAGLIST and NETIF_F_SG difference
Date: Tue, 02 Mar 2010 02:51:58 +0000 [thread overview]
Message-ID: <1267498318.2819.21.camel@localhost> (raw)
In-Reply-To: <20100301.174024.214216263.davem@davemloft.net>
On Mon, 2010-03-01 at 17:40 -0800, David Miller wrote:
> From: Ben Hutchings <bhutchings@solarflare.com>
> Date: Mon, 01 Mar 2010 12:58:41 +0000
>
> > (I don't know why there are two ways of adding extra data. The latter
> > does not seem to be used often.)
>
> It's the most efficient way to handle IPv4/IPv6 fragmentation and
> reassembly.
But fragmentation results in a series of packets to be transmitted
separately (not gathered) and reassembly is only done at endpoints. So
when would we see a fragment list on the transmit path?
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-03-02 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 11:02 NETIF_F_FRAGLIST and NETIF_F_SG difference raj ravi
2010-03-01 12:58 ` Ben Hutchings
2010-03-02 1:40 ` David Miller
2010-03-02 2:51 ` Ben Hutchings [this message]
2010-03-02 3:01 ` David Miller
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=1267498318.2819.21.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=mekaviraj@gmail.com \
--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).