linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: mel@skynet.ie (Mel Gorman)
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	Yasunori Goto <y-goto@jp.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Page allocator: Clean up pcp draining functions
Date: Wed, 14 Nov 2007 18:13:45 +0000	[thread overview]
Message-ID: <20071114181345.GD773@skynet.ie> (raw)
In-Reply-To: <Pine.LNX.4.64.0711121115180.26682@schroedinger.engr.sgi.com>

On (12/11/07 11:17), Christoph Lameter didst pronounce:
> On Mon, 12 Nov 2007, Mel Gorman wrote:
> 
> > Reflecting the comment, perhaps the following would not hurt?
> > 
> > VM_BUG_ON(cpu != smp_processor_id() && cpu_online(cpu))
> 
> Well we need to check first with the hotplug developers if the cpu is 
> already marked off line when this function is called.
> 

Fair point, best left as is for the moment.

> > >  	if (action == CPU_DEAD || action == CPU_DEAD_FROZEN) {
> > > -		local_irq_disable();
> > > -		__drain_pages(cpu);
> > > +		drain_pages(cpu);
> > > +
> > > +		/*
> > > +		 * Spill the event counters of the dead processor
> > > +		 * into the current processors event counters.
> > > +		 * This artificially elevates the count of the current
> > > +		 * processor.
> > > +		 */
> > 
> > This comment addition does not appear to be related to the rest of the
> > patch.
> 
> Its related to the action of vm_events_fold_cpu which is not that 
> unproblematic since the numbers indicate now that more events occurred on 
> this processor than what actually occurred.
> 

Yeah, I've no problem with the comment itself - I just wanted to be sure
it was not part of some other patchset by accident. I'm happy with it
now as-is.

> > Acked-by: Mel Gorman <mel@csn.ul.ie>
> 
> Thanks.
> 

-- 
-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2007-11-14 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  2:44 Christoph Lameter
2007-11-10 12:25 ` Rafael J. Wysocki
2007-11-12 16:04 ` Mel Gorman
2007-11-12 19:17   ` Christoph Lameter
2007-11-14 18:13     ` Mel Gorman [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=20071114181345.GD773@skynet.ie \
    --to=mel@skynet.ie \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=rjw@sisk.pl \
    --cc=y-goto@jp.fujitsu.com \
    /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