From: "Seth, Rohit" <rohit.seth@intel.com>
To: "William Lee Irwin III" <wli@holomorphy.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:52:02 -0700 [thread overview]
Message-ID: <01EF044AAEE12F4BAAD955CB750649430200560D@scsmsx401.amr.corp.intel.com> (raw)
William Lee Irwin III <> wrote on Monday, August 09, 2004 11:59 AM:
> Chen, Kenneth W <mailto:kenneth.w.chen@intel.com> wrote on Monday,
>>> I suppose this is fixable in update_mmu_cache() where it can check
>>> the type of pte and do appropriate sizing and other things. ia64
>>> would have to check the address instead of looking at the pte.
>
> On Mon, Aug 09, 2004 at 11:43:32AM -0700, Seth, Rohit wrote:
>> Why do we need update_mmu_cache for hugepages?
>
> 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.
>
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).
WARNING: multiple messages have this Message-ID (diff)
From: "Seth, Rohit" <rohit.seth@intel.com>
To: William Lee Irwin III <wli@holomorphy.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 08:52:02 +0000 [thread overview]
Message-ID: <01EF044AAEE12F4BAAD955CB750649430200560D@scsmsx401.amr.corp.intel.com> (raw)
In-Reply-To: <200408051329.i75DT3Y26431@unix-os.sc.intel.com>
William Lee Irwin III <> wrote on Monday, August 09, 2004 11:59 AM:
> Chen, Kenneth W <mailto:kenneth.w.chen@intel.com> wrote on Monday,
>>> I suppose this is fixable in update_mmu_cache() where it can check
>>> the type of pte and do appropriate sizing and other things. ia64
>>> would have to check the address instead of looking at the pte.
>
> On Mon, Aug 09, 2004 at 11:43:32AM -0700, Seth, Rohit wrote:
>> Why do we need update_mmu_cache for hugepages?
>
> 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.
>
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).
next reply other threads:[~2004-08-10 8:56 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 8:52 Seth, Rohit [this message]
2004-08-10 8:52 ` Hugetlb demanding paging for -mm tree Seth, Rohit
2004-08-10 8:55 ` William Lee Irwin III
2004-08-10 8:55 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2004-08-11 6:36 Seth, Rohit
2004-08-11 6:36 ` Seth, Rohit
2004-08-11 6:38 ` William Lee Irwin III
2004-08-11 6:38 ` William Lee Irwin III
2004-08-11 0:28 Seth, Rohit
2004-08-11 0:28 ` Seth, Rohit
2004-08-11 0:45 ` William Lee Irwin III
2004-08-11 0:45 ` William Lee Irwin III
2004-08-09 18:43 Seth, Rohit
2004-08-09 18:43 ` Seth, Rohit
2004-08-09 18:59 ` William Lee Irwin III
2004-08-09 18:59 ` William Lee Irwin III
2004-08-05 13:29 Chen, Kenneth W
2004-08-05 13:29 ` Chen, Kenneth W
2004-08-05 13:36 ` William Lee Irwin III
2004-08-05 13:36 ` William Lee Irwin III
2004-08-05 13:39 ` Chen, Kenneth W
2004-08-05 13:39 ` Chen, Kenneth W
2004-08-05 16:35 ` Hirokazu Takahashi
2004-08-05 16:35 ` Hirokazu Takahashi
2004-08-06 20:55 ` Chen, Kenneth W
2004-08-06 20:55 ` Chen, Kenneth W
2004-08-06 21:07 ` William Lee Irwin III
2004-08-06 21:07 ` William Lee Irwin III
2004-08-07 8:13 ` William Lee Irwin III
2004-08-07 8:13 ` William Lee Irwin III
2004-08-09 18:19 ` Chen, Kenneth W
2004-08-09 18:19 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III
2004-08-09 19:12 ` William Lee Irwin III
2004-08-07 8:36 ` William Lee Irwin III
2004-08-07 8:36 ` William Lee Irwin III
2004-08-09 18:54 ` Chen, Kenneth W
2004-08-09 18:54 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III
2004-08-09 19:12 ` William Lee Irwin III
2004-08-05 13:42 ` Chen, Kenneth W
2004-08-05 13:42 ` Chen, Kenneth W
2004-08-05 14:04 ` Andi Kleen
2004-08-05 14:04 ` Andi Kleen
2004-08-06 21:06 ` Chen, Kenneth W
2004-08-06 21:06 ` Chen, Kenneth W
2004-08-05 13:43 ` Andi Kleen
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=01EF044AAEE12F4BAAD955CB750649430200560D@scsmsx401.amr.corp.intel.com \
--to=rohit.seth@intel.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
--cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.