From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: abo@kth.se, openafs-devel@openafs.org, opendce@opengroup.org,
selinux@tycho.nsa.gov, linux-kernel@vger.kernel.org
Subject: Re: Using fuse for AFS/DFS (was Re: [OpenAFS-devel] openafs / opendfs collaboration)
Date: Sun, 30 Jan 2005 13:06:29 +0000 [thread overview]
Message-ID: <20050130130629.GC10895@lkcl.net> (raw)
In-Reply-To: <E1CvENX-0006fY-00@dorka.pomaz.szeredi.hu>
On Sun, Jan 30, 2005 at 01:40:35PM +0100, Miklos Szeredi wrote:
> > the kernel-part of fuse tells any kernel-level callers to
> > "go away, come back later".
> >
> > obviously this gives time for the kernel-part to "wake up" the
> > userspace daemon, obtain an answer, such that when the kernel-level
> > caller _does_ come back, the information is available.
>
> It doesn't do that and never did. ERESTARTSYS is only returned if the
> operation is interrupted, and in that case the operation is restarted
> from scratch, the answer to the old request is never used.
oh??
*confused* - well that's good, then! glad that's cleared up!
[must contact you again about this when i have time]
> > in a nutshell, inodes is an optimisation from a unix
> > perspective: by providing an inode based interface, you are
> > burdening _all_ filesystem implementers with that concept.
>
> Yes. However I think the burden on performance (nothing else), is
> justified by the better flexibility.
i understand.
l.
prev parent reply other threads:[~2005-01-30 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.A41.4.31.0501181606230.24934-100000@slickville.cac.psu.edu>
[not found] ` <Pine.GSO.4.61-042.0501210900060.15636@johnstown.andrew.cmu.edu>
[not found] ` <20050121152803.GB29598@jadzia.bu.edu>
[not found] ` <Pine.GSO.4.61-042.0501211222080.15636@johnstown.andrew.cmu.edu>
[not found] ` <1106923508.7063.37.camel@tudor.e.kth.se>
2005-01-30 3:30 ` Using fuse for AFS/DFS (was Re: [OpenAFS-devel] openafs / opendfs collaboration) Luke Kenneth Casson Leighton
2005-01-30 11:13 ` Miklos Szeredi
2005-01-30 12:13 ` Luke Kenneth Casson Leighton
2005-01-30 12:40 ` Miklos Szeredi
2005-01-30 13:06 ` Luke Kenneth Casson Leighton [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=20050130130629.GC10895@lkcl.net \
--to=lkcl@lkcl.net \
--cc=abo@kth.se \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=openafs-devel@openafs.org \
--cc=opendce@opengroup.org \
--cc=selinux@tycho.nsa.gov \
/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).