From: Ben Hutchings <bhutchings@solarflare.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: <netdev@vger.kernel.org>
Subject: Re: Generating fragmented skb
Date: Wed, 6 Nov 2013 19:01:57 +0000 [thread overview]
Message-ID: <1383764517.1520.16.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6026B73E6@saturn3.aculab.com>
On Wed, 2013-11-06 at 12:31 +0000, David Laight wrote:
> What is the easiest way to generate fragmented skb?
[...]
TCP usually generates fragmented skbs when the output device supports
them, separating the payload (may be transmitted multiple times, not
modified by the stack) from the headers (regenerated by the stack for
each transmission). For small sends this is no longer the case.
You can use sendfile() to control fragmentation from userland.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-11-06 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 12:31 Generating fragmented skb David Laight
2013-11-06 19:01 ` Ben Hutchings [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=1383764517.1520.16.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=David.Laight@ACULAB.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