public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Adam Litke <agl@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: 10 May 2006 23:38:48 +0200	[thread overview]
Message-ID: <p73vesd7e6v.fsf@bragg.suse.de> (raw)
In-Reply-To: <1147287400.24029.81.camel@localhost.localdomain>

Adam Litke <agl@us.ibm.com> writes:

> The following patch enables demotion of MAP_PRIVATE hugetlb memory to
> normal anonymous memory on the i386 architecture.  Below is a short
> description of the problem from a previous posting.


I'm not sure it's a good idea really. I think people have the reasonable
expection that if you use hugetlb you really get huge pages.

If you really implement you should at least printk clearly. But it's 
probably better to not implement it.

If there was generic transparent hugepages support in the VM the case
would be probably different. Then it would make sense. But not as part
of hugetlbfs.

-Andi

  parent reply	other threads:[~2006-05-10 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 18:56 [RFC] Hugetlb demotion for x86 Adam Litke
2006-05-10 19:46 ` Dave Hansen
2006-05-10 19:49 ` Dave Hansen
2006-05-10 20:05 ` Christoph Hellwig
2006-05-10 20:32   ` Adam Litke
2006-05-10 20:49     ` Christoph Hellwig
2006-05-10 21:45       ` Adam Litke
2006-05-11 15:15         ` Hugh Dickins
2006-05-11 15:33           ` Alan Cox
2006-05-11 15:59           ` Adam Litke
2006-05-10 21:38 ` Andi Kleen [this message]
2006-05-10 23:42 ` Christoph Lameter
2006-05-11 16:10   ` Adam Litke
2006-05-15 14:20     ` Dave Hansen

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=p73vesd7e6v.fsf@bragg.suse.de \
    --to=ak@suse.de \
    --cc=agl@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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