From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] afid and fd, mapping from user space
Date: Thu, 7 Jul 2005 06:38:51 -0400 [thread overview]
Message-ID: <ee9e417a050707033835b5c620@mail.gmail.com> (raw)
In-Reply-To: <37ef730aacf5a0b86b77caaa538afd8d@vitanuova.com>
As long as you don't use it for such things (i.e. use it for a real file
system and don't depend on atomic stuff like locks)
I don't see a problem. I used it in 3e for quite a while and never
had any problems. I had to use special bindings to make sure
I didn't try to deliver mail over it, but other than that it was great.
Russ
On 7/6/05, rog@vitanuova.com <rog@vitanuova.com> wrote:
> > I am porting Recover to 4e. Recover is a filesystem which speaks
> > 9P with two ends, a server and a client. When a connection falls down
> > it pushes the state and restarts the pending requests, so you don't
> > see a hung channel any more if your connection falls down.
>
> i did something like this for inferno, but couldn't work out what was
> the best thing to do about non-idempotent 9p transactions: if the
> connection is lost before the reply to such a transaction is received,
> what is the correct course of action? the client can't know whether the
> transaction has actually taken place on the server.
>
> examples of such requests:
>
> create
> wstat (rename)
> write to an append-only file
> any operation on a non-standard filesystem (e.g. writing a ctl file)
>
> problems arising from this kind of thing will be
> rare, but all the more insidious when they do actually happen.
>
> in the end, i decided to make such requests yield Rerror("operation possibly failed"),
> but i have a niggling feeling that the whole approach is wrong.
>
> thoughts?
>
>
prev parent reply other threads:[~2005-07-07 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 22:20 Gorka guardiola
2005-07-02 23:46 ` Russ Cox
2005-07-03 21:48 ` Gorka guardiola
2005-07-07 2:33 ` rog
2005-07-07 10:38 ` Russ Cox [this message]
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=ee9e417a050707033835b5c620@mail.gmail.com \
--to=russcox@gmail.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).