From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Christoph Lameter <clameter@sgi.com>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
raybry@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Hugepages demand paging V1 [3/4]: Overcommit handling
Date: Fri, 22 Oct 2004 04:21:01 -0700 [thread overview]
Message-ID: <20041022112101.GR17038@holomorphy.com> (raw)
In-Reply-To: <20041022111626.GA18037@infradead.org>
On Fri, Oct 22, 2004 at 12:01:16PM +0100, Christoph Hellwig wrote:
>>> overcommit for huge pages sounds like a realy bad idea. Care to explain
>>> why you want it?
On Fri, Oct 22, 2004 at 04:12:59AM -0700, William Lee Irwin III wrote:
> > It's the opposite of what its name implies; it implements strict
> > non-overcommit, in the sense that it tries to prevent the sum of
> > possible hugetlb allocations arising from handling hugetlb faults from
> > exceeding the size of the hugetlb memory pool.
On Fri, Oct 22, 2004 at 12:16:26PM +0100, Christoph Hellwig wrote:
> I thought that was the state of the art for hugetlb pages already?
Only vacuously so, for mainline is not handling hugetlb faults.
The real impediment to all this is that no one is bothering to dredge
up architecture manuals for the architectures they're touching to
create plausible equivalents of update_mmu_cache(), clear_dcache_page()
(not considered by Lameter's patches at all), et al for hugetlb.
-- wli
next prev parent reply other threads:[~2004-10-22 11:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B05667366EE6204181EABE9C1B1C0EB501F2ADFB@scsmsx401.amr.corp.intel.com>
2004-10-22 4:55 ` Hugepages demand paging V1 [0/4]: Discussion and overview Christoph Lameter
2004-10-22 4:56 ` Hugepages demand paging V1 [1/4]: demand paging core Christoph Lameter
2004-10-22 10:47 ` William Lee Irwin III
2004-10-22 15:33 ` Christoph Lameter
2004-10-22 4:57 ` Hugepages demand paging V1 [2/4]: set_huge_pte() arch updates Christoph Lameter
2004-10-22 10:37 ` William Lee Irwin III
2004-10-22 15:32 ` Christoph Lameter
2004-10-22 15:42 ` William Lee Irwin III
2004-10-22 20:29 ` Christoph Lameter
2004-10-22 20:45 ` William Lee Irwin III
2004-10-22 20:49 ` Christoph Lameter
2004-10-22 4:58 ` Hugepages demand paging V1 [3/4]: Overcommit handling Christoph Lameter
2004-10-22 10:28 ` Andrew Morton
2004-10-22 15:08 ` Christoph Lameter
2004-10-22 15:32 ` Chen, Kenneth W
2004-10-22 10:49 ` William Lee Irwin III
2004-10-22 11:01 ` Christoph Hellwig
2004-10-22 11:12 ` William Lee Irwin III
2004-10-22 11:16 ` Christoph Hellwig
2004-10-22 11:21 ` William Lee Irwin III [this message]
2004-10-22 11:23 ` William Lee Irwin III
2004-10-22 4:58 ` Hugepages demand paging V1 [4/4]: Numa patch Christoph Lameter
2004-10-22 6:05 ` Chen, Kenneth W
2004-10-22 11:00 ` William Lee Irwin III
2004-10-22 19:37 ` Christoph Lameter
2004-10-22 19:40 ` William Lee Irwin III
2004-10-25 21:25 ` Chen, Kenneth W
2004-10-25 21:52 ` William Lee Irwin III
2004-10-25 21:55 ` William Lee Irwin III
2004-10-25 21:05 ` Chen, Kenneth W
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=20041022112101.GR17038@holomorphy.com \
--to=wli@holomorphy.com \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raybry@sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).