From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ken Preslan <kpreslan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patch to allow distributed flock
Date: Thu, 24 Jun 2004 21:47:14 -0400 [thread overview]
Message-ID: <1088128034.8906.49.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1088127425.8906.40.camel@lade.trondhjem.org>
På to , 24/06/2004 klokka 21:37, skreiv Trond Myklebust:
> På to , 24/06/2004 klokka 20:07, skreiv Ken Preslan:
>
> > If the FS is managing the posix locks and/or flocks, is there really a
> > reason to acquire the VFS versions of the locks too? As long as there is
> > some bit set that tells the VFS to call down into the FS to unlock the
> > locks on process exit, keeping both sets of locks seems wasteful.
> > What am I missing?
...Oh I forgot to mention --- If you want to support mandatory locks (?)
then the VFS interface can serve as a billboard for posting those
regions of the file that are off-limits to other processes.
Cheers,
Trond
prev parent reply other threads:[~2004-06-25 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:10 Ken Preslan
2004-06-24 23:52 ` Trond Myklebust
2004-06-25 0:07 ` Ken Preslan
2004-06-25 1:37 ` Trond Myklebust
2004-06-25 1:47 ` Trond Myklebust [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=1088128034.8906.49.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=kpreslan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®