From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Hugetlbfs and hugetlb_page config menu
Date: Fri, 26 Sep 2003 23:11:16 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106461789029929@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Hugetlbfs is not module'able at current state, so tristate the "HugeTLB
file system support" option is kind of silly. Also, at present you can
set CONFIG_HUGETLB_PAGE and not CONFIG_HUGETLBFS, which give the kernel
low-level hugepage support, but no userspace API to access it is also
kind of silly.
While I'm at it, here is a patch that flips dependency around:
CONFIG_HUGETLB_PAGE mirrors CONFIG_HUGETLBFS option and hugetlb page
size selection appear/disappear depending on whether hugetlbfs is
selected or not. (this is taken from 2.6).
- Ken
[-- Attachment #2: hugetlbfs-config.patch --]
[-- Type: application/octet-stream, Size: 1094 bytes --]
diff -Nur 2.4.23-pre5/arch/ia64/config.in 2.4.23-pre5.ken/arch/ia64/config.in
--- 2.4.23-pre5/arch/ia64/config.in Fri Sep 26 14:21:54 2003
+++ 2.4.23-pre5.ken/arch/ia64/config.in Fri Sep 26 15:55:20 2003
@@ -86,8 +86,6 @@
define_int CONFIG_FORCE_MAX_ZONEORDER 19
-bool 'IA-64 Huge TLB Page Support' CONFIG_HUGETLB_PAGE
-
if [ "$CONFIG_HUGETLB_PAGE" = "y" ]; then
if [ "$CONFIG_MCKINLEY" = "y" ]; then
choice ' IA-64 Huge TLB Page Size' \
diff -Nur 2.4.23-pre5/fs/Config.in 2.4.23-pre5.ken/fs/Config.in
--- 2.4.23-pre5/fs/Config.in Fri Sep 26 14:22:03 2003
+++ 2.4.23-pre5.ken/fs/Config.in Fri Sep 26 15:56:51 2003
@@ -54,8 +54,11 @@
bool 'Virtual memory file system support (former shm fs)' CONFIG_TMPFS
define_bool CONFIG_RAMFS y
-if [ "$CONFIG_HUGETLB_PAGE" = "y" ]; then
- tristate 'HugeTLB file system support' CONFIG_HUGETLBFS
+bool 'HugeTLB file system support' CONFIG_HUGETLBFS
+if [ "$CONFIG_HUGETLBFS" = "y" ]; then
+ define_bool CONFIG_HUGETLB_PAGE y
+else
+ define_bool CONFIG_HUGETLB_PAGE n
fi
tristate 'ISO 9660 CDROM file system support' CONFIG_ISO9660_FS
reply other threads:[~2003-09-26 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-106461789029929@msgid-missing \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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