From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Tom Herbert" <therbert@google.com>,
"Maciej Żenczykowski" <maze@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: Re: [PATCH net-next] tcp: introduce tcp_try_coalesce
Date: Tue, 24 Apr 2012 04:29:29 +0200 [thread overview]
Message-ID: <1335234569.5205.100.camel@edumazet-glaptop> (raw)
In-Reply-To: <1335233611.5205.90.camel@edumazet-glaptop>
On Tue, 2012-04-24 at 04:13 +0200, Eric Dumazet wrote:
> This never happens on connections where performance matters : skb head
> can only contains one full mss segment.
By the way, top end hardware uses fragged skbs.
Incidentally this gives better splice() performance (avoids copy of skb
head to pages)
next prev parent reply other threads:[~2012-04-24 2:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 17:11 [PATCH net-next] tcp: introduce tcp_try_coalesce Eric Dumazet
2012-04-24 1:13 ` Neal Cardwell
2012-04-24 2:13 ` Eric Dumazet
2012-04-24 2:29 ` Eric Dumazet [this message]
2012-04-24 2:39 ` Neal Cardwell
2012-04-24 2:46 ` David Miller
2012-04-24 2:59 ` Eric Dumazet
2012-04-24 3:34 ` [PATCH net-next] tcp: tcp_try_coalesce returns a boolean Eric Dumazet
2012-04-24 3:37 ` 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=1335234569.5205.100.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=maze@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
/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