All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de
Subject: for_each_online_cpu broken ?
Date: Thu, 8 Dec 2005 00:07:39 -0500	[thread overview]
Message-ID: <20051208050738.GE24356@redhat.com> (raw)

Whilst debugging a memory leak, I hit sysrq meminfo,
and got hot/cold info for CONFIG_NR_CPUS rather than 4 cpus
I fixed a bug recently in mm/page_alloc.c to change this from
a for_each_cpu to a for_each_online_cpu and I'm pretty certain
I tested that it worked, but for reasons unknown, it's now
misbehaving again.

I've only tried reproducing this on x86-64 so far.

		Dave


             reply	other threads:[~2005-12-08  5:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  5:07 Dave Jones [this message]
2005-12-08  5:26 ` for_each_online_cpu broken ? Andi Kleen
2005-12-08  5:33   ` Dave Jones
2005-12-08  5:38     ` David S. Miller
2005-12-08  6:12       ` Andi Kleen
2005-12-08  6:27         ` Dave Jones
2005-12-08  6:22     ` Nigel Cunningham
2005-12-08  6:28       ` Dave Jones
2005-12-08  6:30         ` Andi Kleen
2005-12-09  0:03         ` Nigel Cunningham
2005-12-08  6:30     ` Andi Kleen
2005-12-08  6:43       ` Dave Jones

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=20051208050738.GE24356@redhat.com \
    --to=davej@redhat.com \
    --cc=ak@suse.de \
    --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 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.