From: Christoph Hellwig <hch@infradead.org>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
hch@infradead.org, Andreas Dilger <adilger@clusterfs.com>
Subject: Re: [RFC] page lock ordering and OCFS2
Date: Fri, 21 Oct 2005 18:57:30 +0100 [thread overview]
Message-ID: <20051021175730.GD22372@infradead.org> (raw)
In-Reply-To: <435928BC.5000509@oracle.com>
On Fri, Oct 21, 2005 at 10:43:24AM -0700, Zach Brown wrote:
> It introduces block_read_full_page() and truncate_inode_pages() derivatives
> which understand the PG_fs_misc special case. It needs a few export patches to
> the core, but the real burden is on OCFS2 to keep these derivatives up to date.
The way you do it looks nice, but the exports aren't a big no-way. That
stuff is far too internal to be exported. Either we can get Andrew to
agree on moving those bits into the codepath for all filesystems or
we need to do some hackery where every functions gets renamed to __function
with an argument int cluster_aware and we have to functions inling them,
one normal and one for cluster filesystems.
next prev parent reply other threads:[~2005-10-21 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 22:20 [RFC] page lock ordering and OCFS2 Zach Brown
2005-10-17 23:17 ` Andrew Morton
2005-10-18 0:40 ` Zach Brown
2005-10-18 1:24 ` Andrew Morton
2005-10-18 8:23 ` Anton Altaparmakov
2005-10-18 17:25 ` Zach Brown
2005-10-18 17:14 ` Zach Brown
2005-10-21 17:43 ` Zach Brown
2005-10-21 17:57 ` Christoph Hellwig [this message]
2005-10-21 20:36 ` Zach Brown
2005-10-21 20:59 ` Andrew Morton
2005-10-21 21:57 ` Zach Brown
2005-10-25 0:03 ` Zach Brown
2005-10-21 17:58 ` Andrew Morton
2005-10-21 20:32 ` Zach Brown
2005-10-17 23:37 ` Badari Pulavarty
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=20051021175730.GD22372@infradead.org \
--to=hch@infradead.org \
--cc=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.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