From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
David Chinner <dgc@sgi.com>
Subject: Re: [patch 01/18] Define functions for page cache handling
Date: Wed, 27 Feb 2008 11:20:36 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0802271118020.32462@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080223152716.51cc3875.akpm@linux-foundation.org>
On Sat, 23 Feb 2008, Andrew Morton wrote:
> But the interfaces which they use (passing and address_space) are quite
> pointless unless we implement variable page size per address_space. And as
> the chances of that ever happening seem pretty damn small, these changes
> are just obfuscation which make the code harder to read and which
> pointlessly churn the codebase.
>
> So I'm inclined to drop these patches.
Ummm.. I can submit the rest of the code to make this work? The rest is
available at git://git.kernel.org/pub/scm/linux/kernel/git/christoph/vm.git
Branches
vcompound Fallback for compound pages to order 0 allocs
largeblock Based on vcompound, large block support for devices and FS.
next prev parent reply other threads:[~2008-02-27 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 0:47 [patch 00/18] Page cache: Replace PAGE_CACHE_xx with inline functions V4 Christoph Lameter
2008-02-16 0:47 ` [patch 01/18] Define functions for page cache handling Christoph Lameter
2008-02-23 23:27 ` Andrew Morton
2008-02-27 19:20 ` Christoph Lameter [this message]
2008-02-16 0:47 ` [patch 02/18] Use page_cache_xxx functions in mm/filemap.c Christoph Lameter
2008-02-16 0:47 ` [patch 03/18] Use page_cache_xxx in mm/page-writeback.c Christoph Lameter
2008-02-16 0:47 ` [patch 04/18] Use page_cache_xxx in mm/truncate.c Christoph Lameter
2008-02-16 0:47 ` [patch 05/18] Use page_cache_xxx in mm/rmap.c Christoph Lameter
2008-02-16 0:47 ` [patch 06/18] Use page_cache_xxx in mm/filemap_xip.c Christoph Lameter
2008-02-16 0:47 ` [patch 07/18] Use page_cache_xxx in mm/migrate.c Christoph Lameter
2008-02-16 0:47 ` [patch 08/18] Use page_cache_xxx in fs/libfs.c Christoph Lameter
2008-02-16 0:47 ` [patch 09/18] Use page_cache_xxx in fs/sync Christoph Lameter
2008-02-16 0:47 ` [patch 10/18] Use page_cache_xxx in fs/buffer.c Christoph Lameter
2008-02-16 0:47 ` [patch 11/18] Use page_cache_xxx in mm/mpage.c Christoph Lameter
2008-02-16 0:47 ` [patch 12/18] Use page_cache_xxx in mm/fadvise.c Christoph Lameter
2008-02-16 0:47 ` [patch 13/18] Use page_cache_xxx in fs/splice.c Christoph Lameter
2008-02-16 0:47 ` [patch 14/18] Use page_cache_xxx in ext2 Christoph Lameter
2008-02-16 0:47 ` [patch 15/18] Use page_cache_xxx in fs/ext3 Christoph Lameter
2008-02-16 0:47 ` [patch 16/18] Use page_cache_xxx in fs/ext4 Christoph Lameter
2008-02-16 0:47 ` [patch 17/18] Use page_cache_xxx in fs/reiserfs Christoph Lameter
2008-02-16 0:47 ` [patch 18/18] Use page_cache_xxx for fs/xfs Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2007-12-27 5:32 [patch 00/18] Page cache: Replace PAGE_CACHE_xx with inline functions V3 Christoph Lameter
2007-12-27 5:32 ` [patch 01/18] Define functions for page cache handling Christoph Lameter
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=Pine.LNX.4.64.0802271118020.32462@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).