From: Daniel Phillips <phillips@arcor.de>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
"Peter J. Braam" <braam@clusterfs.com>,
linux-kernel@vger.kernel.org, axboe@suse.de, kevcorry@us.ibm.com,
arjanv@redhat.com, viro@parcelfarce.linux.theplanet.co.uk,
trond.myklebust@fys.uio.no, anton@samba.org,
lustre-devel@clusterfs.com
Subject: Re: [PATCH/RFC] Lustre VFS patch, version 2
Date: Fri, 4 Jun 2004 01:03:54 -0400 [thread overview]
Message-ID: <200406040103.54672.phillips@arcor.de> (raw)
In-Reply-To: <20040603141922.GI4423@marowsky-bree.de>
On Thursday 03 June 2004 10:19, Lars Marowsky-Bree wrote:
> The hooks (once cleaned up, no disagreement here, the technical feedback
> so far has been very valuable and continues to be) are useful and in
> effect needed not just for Lustre, but in principle for all cluster
> filesystems, such as (Open)GFS and others, even potentially NFS4 et al.
GFS is now down to needing two trivial patches:
1) export sync_inodes_sb
2) provide a filesystem hook for flock
Since GFS functions well without any of the current batch of proposed vfs
hooks, the word "needed" is not appropriate. Maybe there is something in
here that could benefit GFS, most probably in the intents department, but we
certainly do want to try it first before pronouncing on that. The raw_ops
seem to be entirely irrelevant to GFS, which is peer-to-pear, so does not
delegate anything to a server. I don't think we have a use for lookup_last.
There are quite possibly some helpful ideas in the dcache tweaks but the devil
is in the details: again we need to try it.
Such things as:
+#define DCACHE_LUSTRE_INVALID 0x0020 /* invalidated by Lustre */
clearly fail the "needed not just for Lustre" test.
Looking into my crystal ball, I see many further revisions of this patch set.
Unfortunately, in the latest revision we lost the patch-by-patch discussion,
which seems to have been replaced by list of issues sorted by complainant.
That's interesting, but it's no substitute.
Regards,
Daniel
next prev parent reply other threads:[~2004-06-04 5:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:15 [PATCH/RFC] Lustre VFS patch, version 2 Peter J. Braam
2004-06-03 13:59 ` Christoph Hellwig
2004-06-03 14:19 ` Lars Marowsky-Bree
2004-06-03 14:26 ` Christoph Hellwig
2004-06-03 14:33 ` Christoph Hellwig
2004-06-03 14:49 ` Trond Myklebust
2004-06-03 18:10 ` Jan Harkes
2004-06-04 5:03 ` Daniel Phillips [this message]
2004-06-03 14:27 ` Christoph Hellwig
2004-06-04 16:55 ` Anton Blanchard
2004-06-07 18:02 ` Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 15:53 Peter J. Braam
2004-06-06 17:00 ` Christoph Hellwig
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=200406040103.54672.phillips@arcor.de \
--to=phillips@arcor.de \
--cc=anton@samba.org \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=braam@clusterfs.com \
--cc=hch@infradead.org \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=lustre-devel@clusterfs.com \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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