From: Rick Jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Subject: Re: [PATCH] Super TSO v3
Date: Tue, 24 May 2005 09:12:21 -0700 [thread overview]
Message-ID: <42935265.3040103@hp.com> (raw)
In-Reply-To: <20050523.193817.112290763.davem@davemloft.net>
David S. Miller wrote:
> From: Herbert Xu <herbert@gondor.apana.org.au>
> Date: Tue, 24 May 2005 12:32:57 +1000
>
>
>>True, the Nagle algorithm itself aims to do something different
>>from this function. However, the act of turning Nagle off is
>>an indication that the application wants to minimise the latency
>>by sending things out ASAP. So we should either respect that
>>here by not delaying the packets to increase the TSO size, or
>>we'll need a new socket option to do that for TSO.
>
>
> Sure, we can check tp->nonagle to turn this deferring off.
>
> But, I bet there are folks who want traditional Nagle turned
> off, yet TSO chunking enabled.
I'm not sure there will be very many of those. I would have thought the folks
who turn-off Nagle are typically doing small sends. If they were not wanting
to wait to aggregate their small sends into MSS segments, or wait for the RTT, I
doubt thet are looking to wait to aggregate to something larger than the MSS.
rick jones
next prev parent reply other threads:[~2005-05-24 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 19:19 [PATCH] Super TSO v3 David S. Miller
2005-05-23 21:34 ` Herbert Xu
2005-05-23 21:50 ` David S. Miller
2005-05-24 0:32 ` Herbert Xu
2005-05-24 2:29 ` David S. Miller
2005-05-24 2:32 ` Herbert Xu
2005-05-24 2:38 ` David S. Miller
2005-05-24 16:12 ` Rick Jones [this message]
2005-05-24 23:42 ` Stephen Hemminger
2005-05-25 0:51 ` David S. 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=42935265.3040103@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).