[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b040c32a0703240011ib9a66f3l1701b8adda94401d@mail.gmail.com>
Date: Sat, 24 Mar 2007 00:11:32 -0700
From: "Ken Chen" <kenchen@...gle.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Nish Aravamudan" <nish.aravamudan@...il.com>,
"Adam Litke" <agl@...ibm.com>,
"Arjan van de Ven" <arjan@...radead.org>,
"William Lee Irwin III" <wli@...omorphy.com>,
"Christoph Hellwig" <hch@...radead.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [patch] rfc: introduce /dev/hugetlb
On 3/23/07, Andrew Morton <akpm@...ux-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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists