From: Andrew Morton <akpm@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove More Unneccessary CPU Notifiers
Date: Sat, 24 Jan 2004 10:10:39 -0800 [thread overview]
Message-ID: <20040124101039.296c34fd.akpm@osdl.org> (raw)
In-Reply-To: <20040124121909.93C8F2C222@lists.samba.org>
Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> Three more removed CPU notifiers extracted from the hotplug CPU patch.
>
> kernel/softirq.c: the tasklet cpu prepration callback is useless:
> the vectors are already initialized to NULL. Even with the hotplug
> CPU patches, they're of little or no use.
>
> fs/buffer.c: once again, they are already initialized to zero.
>
> mm/page_alloc.c: once again, already initialized to zero.
But when hot-remove is implemented we will need to migrate a going-away
CPU's per-cpu data into a different CPU's storage area, will we not?
If so, some of these notifiers need to remain in place.
Or are you saying that we should just leave the per-cpu accounting in a
non-zero state when its CPU has gone away, and rely upon the stats
gathering code iterating across all cpu_possible cpus?
That's a bit lame in the case of __get_page_state() at least. We've had
problems with excess CPU consumption in there at times and it would be good
to be able to change that function to iterate across all online CPUs, not
all possible ones. We can do that if we have a notifier which spills the
numbers from the gone-away CPU into the local CPU's slot.
next prev parent reply other threads:[~2004-01-24 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 12:16 Rusty Russell
2004-01-24 18:10 ` Andrew Morton [this message]
2004-01-25 2:23 ` Rusty Russell
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=20040124101039.296c34fd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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®