From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: some Plan9 related ideas
Date: Mon, 17 Oct 2005 13:45:59 +0100 [thread overview]
Message-ID: <20051017124559.GB29494@server4.lensbuddy.com> (raw)
In-Reply-To: <ee9e417a0510170423g641badf2w99e44c79a661e3aa@mail.gmail.com>
On Mon, Oct 17, 2005 at 07:23:39AM -0400, Russ Cox wrote:
> > I was reading old archives, and I'm probably a bit dense; but what is
> > the reason to use the same tag for the three messages?
>
> The reason is you don't have to wait for the response to the first
> before sending the second and third, avoiding two round trip times.
Yes, but what I didn't understand is why you needed to use the same tag,
I thought you could do this without chaning the protocol.
After some discussion in #plan9 we guessed that the reason is threaded
servers...
Could you explain with more detail how it would work from the (threaded)
server POV? I was thinking that the server could use the fid to avoid
threads stepping into each other, and still avoid having to change the
protocol at all...
And I'm still curious what kernel changes nemo was talking about.
Sorry for being dense
uriel
next prev parent reply other threads:[~2005-10-17 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 23:23 [9fans] " Bhanu Nagendra Pisupati
2005-08-30 12:27 ` Sape Mullender
2005-08-30 15:21 ` Francisco Ballesteros
2005-08-30 15:25 ` Francisco Ballesteros
2005-08-30 17:07 ` [9fans] " Dave Eckhardt
2005-08-30 17:33 ` Francisco Ballesteros
2005-08-30 17:46 ` Russ Cox
2005-08-31 5:54 ` [9fans] tcs bug arisawa
2005-08-31 5:57 ` Rob Pike
2005-10-17 7:14 ` [9fans] Re: some Plan9 related ideas Uriel
2005-10-17 11:23 ` Russ Cox
2005-10-17 12:45 ` Uriel [this message]
2005-10-17 13:03 ` Russ Cox
2005-10-17 13:22 ` Uriel
2005-10-17 15:14 ` Russ Cox
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=20051017124559.GB29494@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--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).