From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Nagle algorithm
Date: Sat, 24 Nov 2001 10:48:12 +0000 [thread overview]
Message-ID: <20011124104817.79873199B9@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
not only that, but the Nagle algorithm explicitly ignores the PSH bit
anyway:
The Nagle algorithm is generally as follows:
If there is unacknowledged data (i.e., SND.NXT >
SND.UNA), then the sending TCP buffers all user
data (regardless of the PSH bit), until the
outstanding data has been acknowledged or until
the TCP can send a full-sized segment (Eff.snd.MSS
bytes; see Section 4.2.2.6).
[-- Attachment #2: Type: message/rfc822, Size: 1733 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Nagle algorithm
Date: Sat, 24 Nov 2001 00:32:31 -0500
Message-ID: <20011124053233.2D3F019A57@mail.cse.psu.edu>
> > i claim it's not the TCP/IP subsystem's responsibility to delay
> > sending something so that it can buffer up writes to make larger
> > packets. that's for stdio or bio (or local OS equivalent).
>
> If there was a way for the user say when to set TCP's PUSH bit,
> would that do the job?
Why would you want this? I thought the above
was a very effective argument.
Russ
next reply other threads:[~2001-11-24 10:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 10:48 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-29 17:33 jmk
2001-11-27 11:28 forsyth
2001-11-27 11:00 forsyth
2001-11-27 5:31 David Gordon Hogan
2001-11-26 12:07 Fco.J.Ballesteros
2001-11-26 11:52 Fco.J.Ballesteros
2001-11-26 11:23 Sean M. Doran
2001-11-26 19:28 ` Dan Cross
2001-11-27 8:57 ` Steve Kilbane
2001-11-27 14:39 ` Boyd Roberts
2001-11-27 19:56 ` Steve Kilbane
2001-11-27 22:26 ` Boyd Roberts
2001-11-29 16:55 ` Matt
2001-11-27 10:16 ` Thomas Bushnell, BSG
2001-11-27 18:59 ` Dan Cross
2001-11-26 11:09 nigel
[not found] <rsc@plan9.bell-labs.com>
2001-11-24 5:32 ` Russ Cox
2001-11-24 20:04 ` Scott Schwartz
2001-11-24 3:26 Scott Schwartz
2001-11-23 11:58 forsyth
2001-11-26 11:07 ` Sean M. Doran
2001-11-26 19:22 ` Dan Cross
2001-11-27 10:16 ` Thomas Bushnell, BSG
2001-11-27 18:55 ` Dan Cross
2001-11-23 9:44 forsyth
2001-11-26 9:59 ` Thomas Bushnell, BSG
2001-11-22 13:24 forsyth
2001-11-22 13:29 ` Boyd Roberts
2001-11-23 9:34 ` Thomas Bushnell, BSG
2001-11-26 19:13 ` Dan Cross
2001-11-21 23:38 David Gordon Hogan
2001-11-21 23:59 ` Andrew Simmons
2001-11-22 9:57 ` Thomas Bushnell, BSG
2001-11-21 23:20 Andrew Simmons
2001-11-26 10:57 ` Sean M. Doran
2001-11-26 19:11 ` Dan Cross
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=20011124104817.79873199B9@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).