lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 24 Mar 2007 00:11:32 -0700
From:	"Ken Chen" <>
To:	"Andrew Morton" <>
Cc:	"Nish Aravamudan" <>,
	"Adam Litke" <>,
	"Arjan van de Ven" <>,
	"William Lee Irwin III" <>,
	"Christoph Hellwig" <>,,
Subject: Re: [patch] rfc: introduce /dev/hugetlb

On 3/23/07, Andrew Morton <> 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
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists