From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] getting a pid from threadpostmountsrv
Date: Sun, 10 Jun 2007 12:14:28 -0400 [thread overview]
Message-ID: <20070610161018.D832E1E8C22@holo.morphisms.net> (raw)
In-Reply-To: <9f691d1a2a08ad4c558f42e502d967ef@9netics.com>
> i handle part of a ns that is exported, with an in-proc
> server. i need to be able to post a note to it.
why?
i know this line of questioning is annoying, but
unless you are posting the note to interrupt a
system call, it's really not a good idea to have
notes flying around in threaded programs.
the problem is that notes can come in at arbitrary
times and really screw things up in unexpected ways.
there is always a better, more coordinated way.
and in the case of interrupting a system call
you'd be better off using iocall and iointerrupt.
russ
next prev parent reply other threads:[~2007-06-10 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 1:39 Skip Tavakkolian
2007-06-10 14:49 ` Russ Cox
2007-06-10 15:57 ` Skip Tavakkolian
2007-06-10 16:14 ` Russ Cox [this message]
2007-06-10 17:32 ` Skip Tavakkolian
2007-06-10 19:56 ` Russ Cox
2007-06-10 18:52 ` Skip Tavakkolian
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=20070610161018.D832E1E8C22@holo.morphisms.net \
--to=rsc@swtch.com \
--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).