From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A little more ado about async Tclunk
Date: Thu, 28 Oct 2010 16:32:08 -0400 [thread overview]
Message-ID: <AANLkTi=yWb7s1Y9P11_2Dw1d92b6rxS85Bx1ZMh4mtpX@mail.gmail.com> (raw)
In-Reply-To: <35dbd2d8996bf96d65c969836bd2e172@terzarima.net>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Thu, Oct 28, 2010 at 4:18 PM, Charles Forsyth <forsyth@terzarima.net>wrote:
> the race is that there's nothing to say that the clunk completes before the
> process continues on to do something more, including some action that
> depends on the clunk completing,
> such as simply repeating the open. that open can fail if the mode or the
> name
> imposes particular constraints; constraints that depend on the order of
> events as
> expressed by the process.
>
Of course, we don't want the process to wait.
On a 'decent' file server, TClunk doesn't do anything that a process would
have to wait for, except invalidate the FID; (I exclude ORCLOSE and OEXCL
files here). Guarding this with MCACHE means that there was already a
statement from the user "I think that this file server is a decent
character.". You can definitely write file servers on which TClunk does
things -- ones in which the right combination of opens and clunks fires the
missiles, for example. This is not for those file servers.
On a decent server, since clunk cannot fail and won't launch the missiles,
you can't really do anything that would depend on the result anyway...
Seem reasonable?
-- vs
[-- Attachment #2: Type: text/html, Size: 1583 bytes --]
next prev parent reply other threads:[~2010-10-28 20:32 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 3:02 Venkatesh Srinivas
2010-10-27 4:23 ` erik quanstrom
2010-10-27 6:27 ` Bruce Ellis
2010-10-27 13:50 ` Charles Forsyth
2010-10-27 13:53 ` Gorka Guardiola
2010-10-27 13:55 ` Francisco J Ballesteros
2010-10-27 14:12 ` John Floren
2010-10-27 14:13 ` Eric Van Hensbergen
2010-10-27 14:48 ` Venkatesh Srinivas
2010-10-27 15:45 ` erik quanstrom
2010-10-27 15:54 ` Venkatesh Srinivas
2010-10-27 21:04 ` Bruce Ellis
2010-10-28 12:12 ` Charles Forsyth
2010-10-28 13:32 ` Bruce Ellis
2010-10-28 14:30 ` Gorka Guardiola
2010-10-28 14:39 ` Gorka Guardiola
2010-10-28 14:58 ` erik quanstrom
2010-10-28 14:41 ` Francisco J Ballesteros
2010-10-28 14:45 ` Eric Van Hensbergen
2010-10-28 14:56 ` Francisco J Ballesteros
2010-10-28 15:37 ` Nathaniel W Filardo
2010-10-28 15:40 ` erik quanstrom
2010-10-28 15:53 ` Francisco J Ballesteros
2010-10-28 19:17 ` Venkatesh Srinivas
2010-10-28 19:24 ` Venkatesh Srinivas
2010-10-28 20:18 ` Charles Forsyth
2010-10-28 20:32 ` Venkatesh Srinivas [this message]
2010-10-28 20:55 ` Nemo
2010-10-28 21:22 ` Venkatesh Srinivas
2010-10-28 22:17 ` Francisco J Ballesteros
2010-10-28 23:51 ` Gorka Guardiola
2010-10-29 5:37 ` Bruce Ellis
2010-10-29 7:44 ` Gorka Guardiola
2010-10-29 8:51 ` Bruce Ellis
2010-10-29 9:01 ` Charles Forsyth
2010-10-29 8:58 ` Bruce Ellis
2010-10-29 16:38 ` Charles Forsyth
2010-10-29 9:45 ` Gorka Guardiola
2010-10-29 9:56 ` Bruce Ellis
2010-10-29 16:01 ` Charles Forsyth
2010-10-29 15:58 ` Venkatesh Srinivas
2010-10-29 16:02 ` roger peppe
2010-10-29 16:17 ` Bruce Ellis
2010-10-29 16:47 ` roger peppe
2010-10-29 16:04 ` Charles Forsyth
2010-10-29 14:14 ` Eric Van Hensbergen
2010-10-29 15:21 ` roger peppe
2010-10-29 15:36 ` erik quanstrom
2010-10-29 15:39 ` Eric Van Hensbergen
2010-10-29 15:49 ` Charles Forsyth
2010-10-29 15:50 ` Eric Van Hensbergen
2010-10-29 15:59 ` Bruce Ellis
2010-10-29 16:28 ` Venkatesh Srinivas
2010-10-29 17:16 ` erik quanstrom
2010-10-29 16:47 ` David Leimbach
2010-10-29 17:13 ` Charles Forsyth
2010-10-29 17:22 ` David Leimbach
2010-10-29 17:26 ` erik quanstrom
2010-10-29 17:47 ` Bruce Ellis
2010-10-29 19:33 ` roger peppe
2010-10-29 20:27 ` Bruce Ellis
2010-10-29 20:41 ` Gorka Guardiola
2010-10-29 20:44 ` Bruce Ellis
2010-10-29 22:31 ` Bakul Shah
2010-10-29 22:39 ` roger peppe
2010-10-29 22:43 ` Bruce Ellis
2010-10-29 23:07 ` roger peppe
2010-10-29 23:28 ` Bruce Ellis
2010-10-30 9:08 ` Nemo
2010-10-31 5:39 ` Bruce Ellis
2010-10-31 8:52 ` roger peppe
2010-10-31 8:57 ` Bruce Ellis
2010-10-31 10:25 ` fgergo
2010-10-31 11:11 ` fgergo
2010-10-31 11:21 ` Bruce Ellis
2010-10-31 11:23 ` roger peppe
2010-10-31 13:06 ` Gorka Guardiola
2010-10-31 13:07 ` Gorka Guardiola
2010-10-31 13:22 ` Gorka Guardiola
2010-11-02 14:29 ` Richard Miller
2010-10-31 14:21 ` Eric Van Hensbergen
2010-10-31 22:17 ` Bruce Ellis
2010-10-31 22:32 ` EBo
2010-10-31 22:41 ` Steve Simon
2010-11-02 13:49 ` Richard Miller
2010-11-02 14:02 ` Eric Van Hensbergen
2010-10-29 18:27 ` David Leimbach
2010-10-29 17:18 ` Charles Forsyth
2010-10-29 17:17 ` erik quanstrom
2010-10-29 17:25 ` David Leimbach
2010-10-29 18:03 ` Eric Van Hensbergen
2010-10-29 18:54 ` Gorka Guardiola
2010-10-29 19:30 ` David Leimbach
2010-10-29 20:20 ` erik quanstrom
2010-10-29 15:55 ` Venkatesh Srinivas
2010-10-29 13:12 ` roger peppe
2010-10-29 13:20 ` Lucio De Re
2010-10-29 15:51 ` Charles Forsyth
2010-10-29 16:36 ` Charles Forsyth
2010-10-27 15:09 ` David Leimbach
2010-10-28 21:39 erik quanstrom
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='AANLkTi=yWb7s1Y9P11_2Dw1d92b6rxS85Bx1ZMh4mtpX@mail.gmail.com' \
--to=me@acm.jhu.edu \
--cc=9fans@9fans.net \
/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).