From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Three random questions
Date: Mon, 28 Jun 2004 17:36:45 +0000 [thread overview]
Message-ID: <200406281735.i5SHZ3Y02989@unix-os.sc.intel.com> (raw)
In-Reply-To: <40E01743.4060309@octopus.com.au>
Duraid Madina wrote on Monday, June 28, 2004 6:04 AM
> 2) What is the Right Way to get huge pages at the moment? I'm running a
> 2.6.5-rc and seem to be running across odd bugs using hugetlbfs.
Check out Documentation/vm/hugetlbpage.txt in the kernel source tree for
a detailed explanation. If you found any bug in this area, please report
to the mailing list. We fixed a few bugs last week. So might be good to
try latest kernel.
> 3) Whatever happened to alloc_hugepages()? That strikes me as vastly (!)
> superior to hugetlbfs, at least for the scientist types who just want to
> escape horrible TLB thrashing.
This was debated on the linux kernel mailing list extensively in the past,
check out the archive.
next prev parent reply other threads:[~2004-06-28 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 13:04 Three random questions Duraid Madina
2004-06-28 17:36 ` Chen, Kenneth W [this message]
2004-06-29 6:16 ` David Mosberger
2004-06-29 14:29 ` Matthew Wilcox
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=200406281735.i5SHZ3Y02989@unix-os.sc.intel.com \
--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