Re: openg and path_to_handle

2006-12-14 Thread Matthew Wilcox
On Thu, Dec 14, 2006 at 03:00:41PM -0600, Rob Ross wrote: I don't think that I understand what you're saying here. The openg() call does not perform file open (not that that is necessarily even a first-class FS operation), it simply does the lookup. When we were naming these calls, from a

Re: openg and path_to_handle

2006-12-14 Thread Rob Ross
Christoph Hellwig wrote: On Wed, Dec 06, 2006 at 03:09:10PM -0700, Andreas Dilger wrote: While it could do that, I'd be interested to see how you'd construct the handle such that it's immune to a malicious user tampering with it, or saving it across a reboot, or constructing one from scratch.

Re: [PATCH 1/10] lockd: add new export operation for nfsv4/lockd locking

2006-12-14 Thread J. Bruce Fields
By the way, one other issue I think we'll need to resolve: On Wed, Dec 06, 2006 at 12:34:11AM -0500, J. Bruce Fields wrote: +/** + * vfs_cancel_lock - file byte range unblock lock + * @filp: The file to apply the unblock to + * @fl: The lock to be unblocked + * + * FL_CANCELED is used to

Re: openg and path_to_handle

2006-12-14 Thread Rob Ross
Matthew Wilcox wrote: On Thu, Dec 14, 2006 at 03:00:41PM -0600, Rob Ross wrote: I don't think that I understand what you're saying here. The openg() call does not perform file open (not that that is necessarily even a first-class FS operation), it simply does the lookup. When we were naming

Re: [NFS] asynchronous locks for cluster exports

2006-12-14 Thread J. Bruce Fields
On Thu, Dec 07, 2006 at 04:51:08PM +, Christoph Hellwig wrote: On Wed, Dec 06, 2006 at 12:34:10AM -0500, J. Bruce Fields wrote: We'd like an asynchronous posix locking interface so that we can provide NFS - We added a new -lock() export operation, figuring this was a feature

statlite()

2006-12-14 Thread Rob Ross
We're going to clean the statlite() call up based on this (and subsequent) discussion and post again. Thanks! Rob Ulrich Drepper wrote: Christoph Hellwig wrote: Ulrich, this in reply to these API proposals: I know the documents. The HECWG was actually supposed to submit an actual draft

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

2006-12-14 Thread Nikolai Joukov
Nikolai Joukov wrote: We have designed a new stackable file system that we called RAIF: Redundant Array of Independent Filesystems. Great! We have performed some benchmarking on a 3GHz PC with 2GB of RAM and U320 SCSI disks. Compared to the Linux RAID driver, RAIF has overheads of

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

2006-12-14 Thread Nikolai Joukov
We started the project in April 2004. Right now I am using it as my /home/kolya file system at home. We believe that at this stage RAIF is mature enough for others to try it out. The code is available at: ftp://ftp.fsl.cs.sunysb.edu/pub/raif/ The code requires no kernel

Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems

2006-12-14 Thread Nikolai Joukov
Well, Congratulations, Doctor!! [Must be nice to be exiled to Stony Brook!! Oh, well, not I] Long Island is a very nice place with lots of vineries and perfect sand beaches - don't envy :-) Here's hoping that source exists, and that it is available for us. I guess, you are subscribed to

Re: [PATCH 1/10] lockd: add new export operation for nfsv4/lockd locking

2006-12-14 Thread Marc Eshel
Lets see if we use export operations or vfs calls. If we do exports we can even add another call just for cancel or maybe we can add a new vfs call. Marc. J. Bruce Fields [EMAIL PROTECTED] wrote on 12/14/2006 03:04:42 PM: By the way, one other issue I think we'll need to resolve: On Wed,