From: Christoph Lameter <clameter@sgi.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Please revert [PATCH] user of the jiffies rounding patch: Slab
Date: Mon, 30 Apr 2007 12:28:07 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704301221490.8075@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <46364017.2040009@linux.intel.com>
On Mon, 30 Apr 2007, Arjan van de Ven wrote:
> Christoph Lameter wrote:
> > Umm you did not read the last bit of the description? It talks about firing
> > all timers on all cpus at once.
> >
>
> it talks about AVOIDING firing all timers on all cpus at once.
Hmmmm... Looked fine right now. Must have gotten the deep end before.
Ok. Could you review the new 1 HZ timer that I added to vmstat.c in mm and
make sure that it does the right thing? I'd like to have that one run at
an jiffy offset of 1 instead of 3 to give you more quiet time.
That one is only used for SMP. With SLUB there will be no periodic timers
at all for UP. SMP only has the vmstats update which should be quite
lightweight compared to the slab reaper and it does not need this long
period between them to be safe.
I'd like to have some ideas from you for NUMA. On NUMA I would like to
have all vm statistics refresh actions on each node be synchronized (which
would also significantly fix the situation on large NUMA for you).
I.e. on HZ the first cpus of each node run vmstats update, on HZ + 1 the
second cpu run its etc. How could we make that work?
prev parent reply other threads:[~2007-04-30 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 21:12 Christoph Lameter
[not found] ` <4633D1A2.6010002@linux.intel.com>
2007-04-28 23:35 ` Christoph Lameter
2007-04-28 23:40 ` Arjan van de Ven
2007-04-30 17:43 ` Christoph Lameter
2007-04-30 19:14 ` Arjan van de Ven
2007-04-30 19:28 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0704301221490.8075@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®