From: William Lee Irwin III <wli@holomorphy.com>
To: "Seth, Rohit" <rohit.seth@intel.com>
Cc: "Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Hirokazu Takahashi <taka@valinux.co.jp>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: Hugetlb demanding paging for -mm tree
Date: Tue, 10 Aug 2004 01:55:31 -0700 [thread overview]
Message-ID: <20040810085531.GI11200@holomorphy.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB750649430200560D@scsmsx401.amr.corp.intel.com>
William Lee Irwin III <> wrote on Monday, August 09, 2004 11:59 AM:
>> As things stand in mainline, it's not an obvious issue. Ken appears to
>> be calling it for hugetlb in the ZFOD fault handling patches, which
>> have the issue that it may behave badly in several respects when
>> acting on large pages. The cache coherency bits in update_mmu_fault()
>> are necessary in general, but mainline omits them. It should only
>> result in intermittent failures on machines with sufficiently
>> incoherent caches.
On Tue, Aug 10, 2004 at 01:52:02AM -0700, Seth, Rohit wrote:
> Will the flush_dcache_page for hugepages even on incoherent caches be
> not enough. And that flush_dcache_page should be done in alloc_hugepage
> after clearing the page(or change the clear_highpage to
> clear_user_high_page).
Could you rephrase that? I'm having trouble figuring out what you meant.
-- wli
next prev parent reply other threads:[~2004-08-10 8:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 8:52 Hugetlb demanding paging for -mm tree Seth, Rohit
2004-08-10 8:55 ` William Lee Irwin III [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-11 6:36 Seth, Rohit
2004-08-11 6:38 ` William Lee Irwin III
2004-08-11 0:28 Seth, Rohit
2004-08-11 0:45 ` William Lee Irwin III
2004-08-09 18:43 Seth, Rohit
2004-08-09 18:59 ` William Lee Irwin III
2004-08-05 13:29 Chen, Kenneth W
2004-08-05 13:36 ` William Lee Irwin III
2004-08-05 13:39 ` Chen, Kenneth W
2004-08-05 16:35 ` Hirokazu Takahashi
2004-08-06 20:55 ` Chen, Kenneth W
2004-08-06 21:07 ` William Lee Irwin III
2004-08-07 8:13 ` William Lee Irwin III
2004-08-09 18:19 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III
2004-08-07 8:36 ` William Lee Irwin III
2004-08-09 18:54 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III
2004-08-05 13:42 ` Chen, Kenneth W
2004-08-05 14:04 ` Andi Kleen
2004-08-06 21:06 ` Chen, Kenneth W
2004-08-05 13:43 ` Andi Kleen
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=20040810085531.GI11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohit.seth@intel.com \
--cc=taka@valinux.co.jp \
/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