From: "Jared Hulbert" <jaredeh@gmail.com>
To: "Nick Piggin" <npiggin@suse.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Carsten Otte" <cotte@de.ibm.com>,
"Martin Schwidefsky
Subject: [RFC][PATCH 0/3] xip: no struct pages -- summary
Date: Fri, 7 Mar 2008 20:33:34 -0800 [thread overview]
Message-ID: <6934efce0803072033g3dab6106n32beb61532f365f7@mail.gmail.com> (raw)
[RFC][PATCH 0/3] xip: no struct pages -- summary
This short series extendeds one of Nick Piggins patches for the XIP
overhaul that we've been kicking around. I'm just hoping to get the
API changes reviewed now. I haven't tested this, just compiled what I
can.
So what I'm doing here is swapping out get_xip_page() for
get_xip_mem(). The get_xip_mem() API gives us a kaddr and a pfn. I
thought it worked best to force this kaddr and pfn down through the
block dev's direct_access() API. I'm really unsure if I understand
whether I got the device specific implementations of the new
direct_access() right.
For those interested I'll be updating my git tree at
git.infradead.org/users/jehulber/axfs.git with an updated patch set
Monday.
[1/3] filemap_xip
fs/open.c | 2
include/linux/fs.h | 4 -
mm/fadvise.c | 2
mm/filemap_xip.c | 204 ++++++++++++++++++++++++-----------------------------
mm/madvise.c | 2
5 files changed, 101 insertions(+), 113 deletions(-)
[2/3] direct_access
arch/powerpc/sysdev/axonram.c | 5 +++--
drivers/block/brd.c | 5 +++--
drivers/s390/block/dcssblk.c | 7 +++++--
include/linux/fs.h | 3 ++-
4 files changed, 13 insertions(+), 7 deletions(-)
[3/3] ext2
inode.c | 2 +-
xip.c | 45 ++++++++++++++++++++++++---------------------
xip.h | 9 +++++----
3 files changed, 30 insertions(+), 26 deletions(-)
reply other threads:[~2008-03-08 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6934efce0803072033g3dab6106n32beb61532f365f7@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cotte@de.ibm.com \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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).