From: "Ken Chen" <kenchen@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Nish Aravamudan <nish.aravamudan@gmail.com>,
Adam Litke <agl@us.ibm.com>,
Arjan van de Ven <arjan@infradead.org>,
William Lee Irwin III <wli@holomorphy.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] rfc: introduce /dev/hugetlb
Date: Sat, 24 Mar 2007 00:11:32 -0700 [thread overview]
Message-ID: <b040c32a0703240011ib9a66f3l1701b8adda94401d@mail.gmail.com> (raw)
In-Reply-To: <20070323221225.bdadae16.akpm@linux-foundation.org>
On 3/23/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> a) Ken observes that obtaining private hugetlb memory via hugetlbfs
> involves "fuss".
>
> b) the libhugetlbfs maintainers then go off and implement a no-fuss way of
> doing this.
Hmm, what started this thread was libhugetlbfs maintainer complained
how "fuss" it was to create private hugetlb mapping and suggested an
even bigger kernel change with pagetable_operations API. The new API
was designed with an end goal of introduce /dev/hugetlb (as one of the
feature, they might be thinking more). What motivated me here is to
point out that we can achieve the same goal of having a /dev/hugetlb
with existing hugetlbfs infrastructure and the implementation is
relatively straightforward. What it also buys us is a bit more
flexibility to the end user who wants to use the interface directly.
--
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:[~2007-03-24 7:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 8:44 Ken Chen
2007-03-23 15:03 ` William Lee Irwin III
2007-03-23 21:56 ` Ken Chen
2007-03-23 15:03 ` Mel Gorman
2007-03-23 15:09 ` William Lee Irwin III
2007-03-23 15:15 ` Mel Gorman
2007-03-23 15:30 ` William Lee Irwin III
2007-03-23 22:04 ` Ken Chen
2007-03-23 21:08 ` Benjamin Herrenschmidt
2007-03-24 4:58 ` Andrew Morton
2007-03-24 5:32 ` Nish Aravamudan
2007-03-24 6:12 ` Andrew Morton
2007-03-24 6:57 ` Sam Ravnborg
2007-03-24 7:41 ` Andrew Morton
2007-03-24 7:11 ` Ken Chen [this message]
2007-03-24 7:39 ` Andrew Morton
2007-03-25 10:22 ` Arjan van de Ven
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=b040c32a0703240011ib9a66f3l1701b8adda94401d@mail.gmail.com \
--to=kenchen@google.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nish.aravamudan@gmail.com \
--cc=wli@holomorphy.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