From: Christoph Lameter <clameter@sgi.com>
To: akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Cc: David Chinner <dgc@sgi.com>
Subject: [patch 00/18] Page cache: Replace PAGE_CACHE_xx with inline functions V4
Date: Fri, 15 Feb 2008 16:47:18 -0800 [thread overview]
Message-ID: <20080216004718.047808297@sgi.com> (raw)
This patchset cleans up page cache handling by replacing
open coded shifts and adds with inline function calls.
The ultimate goal is to replace all uses of PAGE_CACHE_xxx in the
kernel through the use of these functions. All the functions take
a mapping parameter. The mapping parameter is required if we want
to support large block sizes in filesystems and block devices.
Patchset against upstream as of today (2.6.25-rc2)
Patchset can be pulled from
git://git.kernel.org/pub/scm/linux/kernel/git/christoph/vm.git pagecache-inline
V2->V4:
- Rediff to upstream. Surprisingly no rejects at all so it seems that all
of the pagecache patches that were in mm were merged. Just had to refresh
the patches.
V2->V3:
- Audit to check that uses of page->mapping are valid. Improve a couple
of places. Make it clearer how the mappings are determined and handled
(see the comments of each patch for detailed descriptions).
- Use a consistent method to determine the mapping if a function already
does determine the inode via page->mapping->host.
V1->V2:
- Review by Dave Chinner. Multiple improvements and fixes.
- Review by Fengguand Wu with more improvements.
--
next reply other threads:[~2008-02-16 0:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 0:47 Christoph Lameter [this message]
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
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
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=20080216004718.047808297@sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--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).