All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zou Nan hai <nanhai.zou@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch 0/3] Page table quicklist fixups Rev 3.
Date: Fri, 04 Mar 2005 08:03:38 +0000	[thread overview]
Message-ID: <1109923418.2525.20.camel@linux-znh> (raw)
In-Reply-To: <20050303212359.GA732@lnx-holt.americas.sgi.com>

On Fri, 2005-03-04 at 16:46, Robin Holt wrote:
> What do you want me to do.  I don't see anywhere else in the kernel
> that these two lines are directly adjacent.  Most places that do
> the disable/enable are in a function which does one thing.  That is
> occasionally contained inside a larger loop.  We can not do that since
> part of our outer loop control is based on the per_cpu variable we are
> expecting to not change.  I suppose I could elminitate the disable/enable
> entirely.  I haven't thought all the way through the possibilities,
> but I would guess we could free a couple extra pages, but who cares.
> You tell me what to do.
> 
> Robin

  I think there is no need to disable preempt in an idle thread...,
since the idle thread has no chance to migrate to another CPU.

  I also think that the shrinking of pgtables is a bit like that in
shrink_slab in vmscan.c, shrink_slab shrinks slab by batch, and itcalls
cond_resched every batch. 
So that it will not introduce too big latency when there are too many
slabs to shrink. 
While shrink_slab is called under mem pressure but check_pdt_cache is
called in idle thread, maybe there is some difference.

Zou Nan hai
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 21:23 [Patch 0/3] Page table quicklist fixups Rev 3 Robin Holt
2005-03-03 21:57 ` Luck, Tony
2005-03-04  8:03 ` Zou Nan hai [this message]
2005-03-04  8:46 ` Robin Holt
2005-03-04 14:55 ` Robin Holt
2005-03-04 16:25 ` Robin Holt
2005-03-04 19:58 ` Luck, Tony
2005-03-04 22:33 ` Chen, Kenneth W
2005-03-07 12:57 ` Robin Holt
2005-03-08 23:56 ` Luck, Tony
2005-03-15 19:33 ` [Patch 0/3] Page table quicklist fixups Rev 4 Robin Holt
2005-03-16  0:24 ` Luck, Tony

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=1109923418.2525.20.camel@linux-znh \
    --to=nanhai.zou@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 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.