All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:45:27 -0700	[thread overview]
Message-ID: <20040811004527.GJ11200@holomorphy.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB750649430205DDE1@scsmsx401.amr.corp.intel.com>

William Lee Irwin III <mailto:wli@holomorphy.com> wrote on Tuesday,
>> Could you rephrase that? I'm having trouble figuring out what you
>> meant. 

On Tue, Aug 10, 2004 at 05:28:27PM -0700, Seth, Rohit wrote:
> I was thinking that we only need to worry about the d-cache coherency at
> the time of hugepage fault.  But that is not a safe assumption.  You are
> right that we will need update_mmu_cache in the hugetlb page fault path.
> Though I'm wondering if we can hide this update_mmu_cache fucntionality
> behind the arch specific set_huge_pte function in the demand paging
> patch for hugepage.  If so then we may not need to make any changes in
> the existing update_mmu_cache API.

Most arches seem to be okay with the API, but it may be more useful/etc.
to e.g. explicitly pass the page size, particularly when constant
folding is possible.


-- wli

WARNING: multiple messages have this Message-ID (diff)
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: Wed, 11 Aug 2004 00:45:27 +0000	[thread overview]
Message-ID: <20040811004527.GJ11200@holomorphy.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB750649430205DDE1@scsmsx401.amr.corp.intel.com>

William Lee Irwin III <mailto:wli@holomorphy.com> wrote on Tuesday,
>> Could you rephrase that? I'm having trouble figuring out what you
>> meant. 

On Tue, Aug 10, 2004 at 05:28:27PM -0700, Seth, Rohit wrote:
> I was thinking that we only need to worry about the d-cache coherency at
> the time of hugepage fault.  But that is not a safe assumption.  You are
> right that we will need update_mmu_cache in the hugetlb page fault path.
> Though I'm wondering if we can hide this update_mmu_cache fucntionality
> behind the arch specific set_huge_pte function in the demand paging
> patch for hugepage.  If so then we may not need to make any changes in
> the existing update_mmu_cache API.

Most arches seem to be okay with the API, but it may be more useful/etc.
to e.g. explicitly pass the page size, particularly when constant
folding is possible.


-- wli

  reply	other threads:[~2004-08-11  0:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11  0:28 Hugetlb demanding paging for -mm tree Seth, Rohit
2004-08-11  0:28 ` Seth, Rohit
2004-08-11  0:45 ` William Lee Irwin III [this message]
2004-08-11  0:45   ` 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-10  8:52 Seth, Rohit
2004-08-10  8:52 ` Seth, Rohit
2004-08-10  8:55 ` William Lee Irwin III
2004-08-10  8:55   ` 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=20040811004527.GJ11200@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 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.