From: Zach Brown <zab@zabbo.net>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: Mark Fasheh <mark.fasheh@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
David Teigland <teigland@redhat.com>,
Pekka Enberg <penberg@gmail.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-cluster@redhat.com, Andreas Dilger <adilger@clusterfs.com>
Subject: Re: GFS
Date: Thu, 11 Aug 2005 09:33:41 -0700 [thread overview]
Message-ID: <42FB7DE5.2080506@zabbo.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508111006470.13379@sbz-30.cs.Helsinki.FI>
> What I meant was that, if a filesystem requires vma walks, we need to do
> it VFS level with something like the following patch.
I don't think this patch is the way to go at all. It imposes an
allocation and vma walking overhead for the vast majority of IOs that
aren't interested. It doesn't look like it will get a consistent
ordering when multiple file systems are concerned. It doesn't record
the ranges of the mappings involved so Lustre can't properly use its
range locks. And finally, it doesn't prohibit mapping operations for
the duration of the IO -- the whole reason we ended up in this thread in
the first place :)
Christoph, would you be interested in looking at a more thorough patch
if I threw one together?
- z
next prev parent reply other threads:[~2005-08-11 16:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 7:10 GFS Pekka J Enberg
2005-08-11 16:33 ` Zach Brown [this message]
2005-08-11 16:35 ` GFS Christoph Hellwig
2005-08-11 16:39 ` GFS Zach Brown
2005-08-11 16:44 ` GFS Pekka Enberg
-- strict thread matches above, loose matches on Subject: below --
2005-08-02 7:18 [PATCH 00/14] GFS David Teigland
2005-08-02 10:16 ` Pekka Enberg
2005-08-03 6:36 ` David Teigland
2005-08-08 14:14 ` GFS Pekka J Enberg
2005-08-08 18:32 ` GFS Zach Brown
2005-08-09 14:49 ` GFS Pekka Enberg
2005-08-09 17:17 ` GFS Zach Brown
2005-08-09 18:35 ` GFS Pekka J Enberg
2005-08-10 4:48 ` GFS Pekka J Enberg
2005-08-10 7:21 ` GFS Christoph Hellwig
2005-08-10 7:31 ` GFS Pekka J Enberg
2005-08-10 16:26 ` GFS Mark Fasheh
2005-08-10 16:57 ` GFS Pekka J Enberg
2005-08-10 18:21 ` GFS Mark Fasheh
2005-08-10 20:18 ` GFS Pekka J Enberg
2005-08-10 22:07 ` GFS Mark Fasheh
2005-08-11 4:41 ` GFS Pekka J Enberg
2005-08-10 5:59 ` GFS David Teigland
2005-08-10 6:06 ` GFS Pekka J Enberg
2005-08-03 6:44 ` [PATCH 00/14] GFS Pekka Enberg
2005-08-08 9:57 ` David Teigland
2005-08-08 10:00 ` GFS Pekka J Enberg
2005-08-08 10:18 ` GFS Pekka J Enberg
2005-08-08 10:56 ` GFS David Teigland
2005-08-08 10:57 ` GFS Pekka J Enberg
2005-08-08 11:39 ` GFS David Teigland
2005-08-08 10:34 ` GFS Pekka J Enberg
2005-08-09 14:55 ` GFS Pekka J Enberg
2005-08-10 7:40 ` GFS Pekka J Enberg
2005-08-10 7:43 ` GFS 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=42FB7DE5.2080506@zabbo.net \
--to=zab@zabbo.net \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=penberg@cs.Helsinki.FI \
--cc=penberg@gmail.com \
--cc=teigland@redhat.com \
/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