From: Hubertus Franke <frankeh@watson.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: schwidefsky@de.ibm.com, linux-mm@kvack.org, akpm@osdl.org,
rhim@cc.gatech.edu
Subject: Re: [patch 1/8] Page host virtual assist: unused / free pages.
Date: Mon, 24 Apr 2006 11:43:46 -0400 [thread overview]
Message-ID: <444CF232.5000003@watson.ibm.com> (raw)
In-Reply-To: <200604241706.27221.ak@suse.de>
Andi Kleen wrote:
> On Monday 24 April 2006 16:59, Martin Schwidefsky wrote:
>
>
>>Ok, sounds reasonable. Do we need to drop the _hva name component? If we
>>do that then something like page_hva_unmap_all will be named
>>page_unmap_all which might be a bit confusing as well.
>
>
> I would drop it because it seems like a very s390 specific term.
>
> -Andi
First, let's decide whether the functionality and the page states
should be considered an "explicit concept" within linux like for instance
the KMAP.
So residency information of the hypervisor is thus exposed in the OS.
Having 3 or 4 states which seem easily understood ( unused, stable, volatile, p-volatile )
seems easy enough to us.
We can drop the _hva_ from the function calls and the name collisions we can
solved differently or leave them there with _hva_ or what ever name makes sense.
They don't show up in the general code path anyway.
Anybody else have a thought on this, Andrew ?
-- Hubertus
--
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:[~2006-04-24 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 12:34 Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
2006-04-24 14:07 ` Andi Kleen
2006-04-24 14:41 ` Martin Schwidefsky
2006-04-24 14:49 ` Andi Kleen
2006-04-24 14:59 ` Martin Schwidefsky
2006-04-24 15:06 ` Andi Kleen
2006-04-24 15:43 ` Hubertus Franke [this message]
2006-04-25 12:20 ` Nick Piggin
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=444CF232.5000003@watson.ibm.com \
--to=frankeh@watson.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=rhim@cc.gatech.edu \
--cc=schwidefsky@de.ibm.com \
/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