From: Andrew Morton <akpm@linux-foundation.org>
To: npiggin@nick.local0.net
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jared Hulbert <jaredeh@gmail.com>,
Carsten Otte <cotte@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-mm@kvack.org
Subject: Re: [patch 0/7] [rfc] VM_MIXEDMAP, pte_special, xip work
Date: Tue, 11 Mar 2008 21:35:25 -0700 [thread overview]
Message-ID: <20080311213525.a5994894.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080311104653.995564000@nick.local0.net>
On Tue, 11 Mar 2008 21:46:53 +1100 npiggin@nick.local0.net wrote:
> --
>
> (doh, please ignore the previous "x/6" patches, they're old. The
> new ones are these x/7 set)
>
> Hi,
>
> I'm sorry for neglecting these patches for a few weeks :(
>
> I'd like to still get them into -mm and aim for the next merge window --
> they've been gradually getting a pretty reasonable amount of review and
> testing. I think the implementation of the pte_special path in vm_normal_page
> and vm_insert_mixed was the only point left unresolved since last time.
>
> I've included the dual kaddr/pfn API that we worked out with Jared, but
> he hasn't yet tested my patch rollup... so this is an RFC only. If we all
> agree on it, then I'll rebase to -mm and submit.
>
umm, could we have some executive summary about what this is all supposed
to achieve? I can see what each patch does, but what's the overall result?
[1/7] says:
> VM_MIXEDMAP achieves this by refcounting all pfn_valid pages, and not
> refcounting !pfn_valid pages (which is not an option for VM_PFNMAP, because
> it needs to avoid refcounting pfn_valid pages eg. for /dev/mem mappings).
I have this vague feeling that pfn_valid() isn't reliable - it can
sometimes lie, and that making it truthful was considered too expensive.
But maybe I'm thinking of something else?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-03-12 4:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 10:46 npiggin
2008-03-11 10:46 ` [patch 1/7] mm: introduce VM_MIXEDMAP npiggin, Jared Hulbert
2008-03-11 10:46 ` [patch 2/7] mm: introduce pte_special pte bit npiggin
2008-03-11 10:46 ` [patch 3/7] mm: add vm_insert_mixed npiggin
2008-03-11 10:46 ` [patch 4/7] Alter the block device ->direct_access() API to work with the new get_xip_mem() API (that requires both kaddr and pfn are returned) npiggin
2008-03-11 10:46 ` [patch 5/7] xip: support non-struct page backed memory npiggin
2008-03-11 11:44 ` [patch 0/7] [rfc] VM_MIXEDMAP, pte_special, xip work Nick Piggin
2008-03-11 21:12 ` Jared Hulbert
2008-03-11 23:21 ` Nick Piggin
2008-03-12 4:35 ` Andrew Morton [this message]
2008-03-12 5:33 ` Nick Piggin
2008-03-12 8:46 ` Martin Schwidefsky
2008-03-12 16:40 ` Jared Hulbert
2008-03-12 17:10 ` Jared Hulbert
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=20080311213525.a5994894.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jaredeh@gmail.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@nick.local0.net \
--cc=schwidefsky@de.ibm.com \
--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