From: Rick Jones <raj@cup.hp.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [Fwd: [Fwd: Is sendfile all that sexy? (fwd)]]
Date: Fri, 19 Jan 2001 11:07:56 -0800 [thread overview]
Message-ID: <3A68908C.3F3FE453@cup.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101181840380.16292-100000@twinlark.arctic.org>
dean gaudet wrote:
>
> On Wed, 17 Jan 2001, Rick Jones wrote:
>
> > > actually the problem isn't nagle... nagle needs to be turned off for
> > > efficient servers anyhow.
> >
> > i'm not sure I follow that. could you expand on that a bit?
>
> the problem which caused us to disable nagle in apache is documented in
> this paper <http://www.isi.edu/~johnh/PAPERS/Heidemann97a.html>. mind you
> i should personally revisit the paper after all these years so that i can
> reconsider its implications in the context of pipelining and webmux.
ah yes, that - where the web server even for just static content was
providing the replies in more than one send. i would not consider that
to have been an "efficient" server.
i'm not sure that I agree with their statment that piggy-backing is
rarely successful in request/response situations.
the business about the last 1100ish bytes of a 4096 byte send being
delayed by nagle only implies that the stack's implementation of nagle
was broken and interpreting it on a per-segment rather than a per-send
basis. if the app sends 4096 bytes, then there should be no
nagle-induced delays on a connection with an MSS of 4096 or less.
it would seem that in the context of that paper at least, most if not
all of the problems were the result of bugs - either in the webserver
software, or the host TCP stack. otherwise, the persistent connections
would have worked just fine.
> i'm not aware yet of any study in the field. and i'm out of touch enough
> with the clients that i don't know if new netscape or IE have finally
> begun to use pipelining (they hadn't as of 1998).
someone else sent a private email implying that no browsers were yet
doing pipelining.
rick
--
ftp://ftp.cup.hp.com/dist/networking/misc/rachel/
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to email, OR post, but please do NOT do BOTH...
my email address is raj in the cup.hp.com domain...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-19 19:08 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A65E825.FFEB194@cup.hp.com>
2001-01-17 19:27 ` [Fwd: [Fwd: Is sendfile all that sexy? (fwd)]] Linus Torvalds
2001-01-17 20:03 ` Rick Jones
2001-01-17 20:38 ` dean gaudet
2001-01-17 20:57 ` Rick Jones
2001-01-18 13:06 ` Ingo Molnar
2001-01-18 14:57 ` Andi Kleen
2001-01-18 18:24 ` Rick Jones
2001-01-19 2:46 ` dean gaudet
2001-01-19 3:03 ` dean gaudet
2001-01-19 19:07 ` Rick Jones [this message]
2001-01-19 20:03 ` kuznet
2001-01-19 21:20 ` Rick Jones
2001-01-20 18:03 ` kuznet
2001-01-22 18:44 ` Rick Jones
2001-01-20 14:56 ` Kai Henningsen
2001-01-23 7:20 ` dean gaudet
2001-01-20 23:09 ` Lincoln Dale
2001-01-20 23:27 ` James Sutherland
2001-01-21 0:02 ` Chris Wedgwood
2001-01-18 12:56 ` Ingo Molnar
2001-01-25 17:58 ` Jamie Lokier
2001-01-17 21:22 ` Linus Torvalds
2001-01-17 22:17 ` Rick Jones
2001-01-17 22:53 ` Linus Torvalds
2001-01-17 22:44 ` Jonathan Walther
2001-01-18 13:18 ` Ingo Molnar
2001-01-18 16:49 ` Linus Torvalds
2001-01-18 17:32 ` Ingo Molnar
2001-01-18 17:49 ` Zach Brown
2001-01-19 3:16 ` dean gaudet
2001-01-19 3:56 ` David Ford
2001-01-18 18:29 ` Rick Jones
2001-01-18 18:50 ` Linus Torvalds
2001-01-18 19:38 ` Andrea Arcangeli
2001-01-18 19:43 ` Ingo Molnar
2001-01-18 19:52 ` Linus Torvalds
2001-01-18 20:11 ` kuznet
2001-01-18 20:33 ` Ingo Molnar
2001-01-18 21:14 ` Andrea Arcangeli
2001-01-18 20:24 ` Andrea Arcangeli
2001-01-18 20:37 ` kuznet
2001-01-18 21:04 ` Andrea Arcangeli
2001-01-19 0:27 ` Olivier Galibert
2001-01-19 0:59 ` Rick Jones
2001-01-19 17:52 ` kuznet
2001-01-19 20:54 ` Andrea Arcangeli
2001-01-18 20:44 ` Ingo Molnar
2001-01-18 21:54 ` Andrea Arcangeli
2001-01-18 21:57 ` Ingo Molnar
2001-01-18 22:16 ` Andrea Arcangeli
2001-01-18 22:18 ` Ingo Molnar
2001-01-19 15:25 ` Andrea Arcangeli
2001-01-19 18:18 ` kuznet
2001-01-19 21:13 ` Andrea Arcangeli
2001-01-20 17:28 ` kuznet
2001-01-20 18:14 ` Abramo Bagnara
2001-01-20 18:23 ` Andrea Arcangeli
2001-01-20 19:05 ` kuznet
2001-01-20 19:30 ` Andrea Arcangeli
2001-01-20 19:39 ` Linus Torvalds
2001-01-20 20:22 ` kuznet
2001-01-20 21:20 ` Andrea Arcangeli
2001-01-20 20:56 ` Andrea Arcangeli
2001-01-21 18:37 ` kuznet
2001-01-20 19:39 ` kuznet
2001-01-20 21:05 ` Andrea Arcangeli
2001-01-20 21:31 ` Guus Sliepen
2001-01-18 22:20 ` Ingo Molnar
2001-01-18 19:45 ` Linus Torvalds
2001-01-18 19:59 ` kuznet
2001-01-18 20:44 ` Andrea Arcangeli
2001-01-19 3:25 ` dean gaudet
2001-01-19 3:35 ` dean gaudet
2001-01-18 9:34 ` Andi Kleen
2001-01-18 18:20 ` Rick Jones
2001-01-18 19:45 ` Andi Kleen
2001-01-18 20:30 ` kuznet
2001-01-18 20:50 ` Ingo Molnar
2001-01-18 22:49 ` Rick Jones
2001-01-18 13:29 ` Ingo Molnar
2001-01-18 16:51 ` Linus Torvalds
2001-01-18 17:04 ` Ingo Molnar
2001-01-17 21:51 Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 0:19 Cacophonix
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=3A68908C.3F3FE453@cup.hp.com \
--to=raj@cup.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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