From: Paul Cameron Davies <pauld@cse.unsw.EDU.AU>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Page Table cleanup patch
Date: Thu, 25 Jan 2007 11:17:22 +1100 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701251116040.4081@weill.orchestra.cse.unsw.EDU.AU> (raw)
In-Reply-To: <45B6CE8C.8010807@yahoo.com.au>
Hi Nick
On Wed, 24 Jan 2007, Nick Piggin wrote:
> Paul Davies wrote:
>> This patch is a proposed cleanup of the current page table organisation.
>> Such a cleanup would be a logical first step towards introducing at least
>> a partial clean page table interface, geared towards providing enhanced
>> virtualization oportunities for x86. It is also a common sense cleanup in
>> its own right.
>>
>> * Creates mlpt.c to hold the page table implementation currently held
>> in memory.c.
>> * Adjust Makefile * Move implementation dependent page table code out of
>> include/linux/mm.h into include/linux/mlpt-mm.h
>> * Move implementation dependent page table code out of
>> include/asm-generic/pgtable.h to include/asm-generic/pgtable-mlpt.h
>>
>> mlpt stands from multi level page table.
>
> Hi Paul,
>
> I'm not sure that I see the point of this patch alone, as there is still
> all the mlpt implementation details in all the page table walkers. Or
> did you have a scheme to change implementations somehow just using the
> p*d_addr_next?
This patch alone doesn't acheive nearly enough. Separating out as much
implementation (without tackling the walkers) would be a start though.
The MLPT appears to be intrinsic to the kernel owing to its open coding,
and starting to isolate its implementation (even partially) is an
important step towards destroying this misconception.
I strongly prefer not to go down the path of using a scheme to change
implementations with p*d_addr_next. I tried this kind of thing early on
and it was horribly ugly. There are far cleaner ways to do it.
Cheers
Paul Davies
--
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>
prev parent reply other threads:[~2007-01-25 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 2:38 Paul Davies
2007-01-24 3:12 ` Nick Piggin
2007-01-25 0:17 ` Paul Cameron Davies [this message]
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.0701251116040.4081@weill.orchestra.cse.unsw.EDU.AU \
--to=pauld@cse.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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