linux-kernel - RE: [RFC] hugetlb: Move hugetlb_get_unmapped

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <000001c6ed4c$08419150$1680030a@amr.corp.intel.com>
Date:	Wed, 11 Oct 2006 08:43:38 -0700
From:	"Chen, Kenneth W" <kenneth.w.chen@...el.com>
To:	"'Adam Litke'" <agl@...ibm.com>, "linux-mm" <linux-mm@...ck.org>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>, <wli@...omorphy.com>
Subject: RE: [RFC] hugetlb: Move hugetlb_get_unmapped_area

Adam Litke wrote on Wednesday, October 11, 2006 6:32 AM
> I am trying to do some hugetlb interface cleanups which include
> separation of the hugetlb utility functions (mostly in mm/hugetlb.c)
> from the hugetlbfs interface to huge pages (fs/hugetlbfs/inode.c).
> 
> This patch simply moves hugetlb_get_unmapped_area() (which I'll argue is
> more of a utility function than an interface) to mm/hugetlb.c.  

To me it doesn't look like a clean up.  get_unmapped_area() is one of
file_operations method and it make sense with the current arrangement
that it stays together with .mmap method, which both live in
fs/hugetlbfs/inode.c.

- Ken
-
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/