From: G. David Butler gdb@dbSystems.com
Subject: [9fans] create(2)/open(2) race for file creation
Date: Sun, 8 Feb 1998 10:16:01 -0600 [thread overview]
Message-ID: <19980208161601.6oERwsfpuvmqjXnjWE3yYGHkCy2xFmVbhj43qR0qtuU@z> (raw)
>From: "Dave Presotto" <presotto@plan9.bell-labs.com>
>This is why I got ken to introduce exclusive access files. I
>use one as a lock for a directory/file/whatever.
I tried that with:
open(lock file in directory)
if open fail {
create
write
close
}
close(lock file)
But the 9p overhead and the bottleneck created convinced me that
it was not a good idea. The above becomes:
open(2)
walk(5)
open(5)
open(2)
walk(5) [fails]
create(2)
walk(5) [create(2) trying to determine to send the create(5)]
create(5)
write(2)...
close(2)
clunk(5)
close(2)
clunk(5)
If we change create(2) to do create(5) then:
if create() success {
write
close
}
becomes:
create(2)
create(5)
write(2)...
close(2)
clunk(5)
Much better.
David Butler
gdb@dbSystems.com
next reply other threads:[~1998-02-08 16:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-08 16:16 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-26 23:30 Russ
1998-02-26 23:01 G.David
1998-02-26 22:16 G.David
1998-02-26 19:33 Eric
1998-02-26 0:24 G.David
1998-02-26 0:04 G.David
1998-02-25 23:42 G.David
1998-02-10 14:34 G.David
1998-02-10 8:59 forsyth
1998-02-09 21:21 G.David
1998-02-09 16:42 G.David
1998-02-09 8:05 Dan
1998-02-08 22:48 G.David
1998-02-08 22:18 Photon
1998-02-08 21:44 Rob
1998-02-08 21:10 G.David
1998-02-08 16:52 G.David
1998-02-08 16:10 Dave
1998-02-08 15:48 G.David
1998-02-08 5:09 G.David
1998-02-08 2:01 Rob
1998-02-08 0:27 G.David
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=19980208161601.6oERwsfpuvmqjXnjWE3yYGHkCy2xFmVbhj43qR0qtuU@z \
--to=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).