public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: How should I proceed with page table caches?
Date: Mon, 14 Mar 2005 19:04:40 +0000	[thread overview]
Message-ID: <200503141904.j2EJ4fg20199@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050314172733.GA11272@lnx-holt.americas.sgi.com>

David Mosberger wrote on Monday, March 14, 2005 10:49 AM
> >>>>> On Mon, 14 Mar 2005 11:27:33 -0600, Robin Holt <holt@sgi.com> said:
>
>   Robin> Tony and David, Is there any chance I can do another push of
>   Robin> the page table cache stuff with the last bits of cleanup and
>   Robin> those getting in without addressing the removal of the
>   Robin> cpu_idle() call?  Neither solution I was given last week
>   Robin> seems particularly well fitted to the problem at hand.  I
>   Robin> would like to get this in so I can continue working on the
>   Robin> 4-level page table directory I am really trying to address.
>
> From memory, the last version I saw looked pretty decent to me.
>
> I agree with Ken's concerns, but given that we have historically done
> page-table cache shrinking from cpu_idle(), your patch doesn't worsen
> the situation (unless I'm missing something), so I think that concern
> could be addressed separately.


I plan to look at set_shrinker API.  But please don't make that as a gating
factor for Robin's patch since I'm not sure when I will be able to get to it
or whether set_shrinker can actually solve the problem (it appears that it
has all the necessary infrastructure).

- Ken



  parent reply	other threads:[~2005-03-14 19:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 17:27 How should I proceed with page table caches? Robin Holt
2005-03-14 18:48 ` David Mosberger
2005-03-14 19:04 ` Chen, Kenneth W [this message]
2005-03-14 19:18 ` Robin Holt

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=200503141904.j2EJ4fg20199@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