All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: keir@xen.org, andrew.cooper3@citrix.com, Tim Deegan <tim@xen.org>,
	xen-devel@lists.xen.org, JBeulich@suse.com,
	Konrad Rzeszutek Wilk <konrad@darnok.org>,
	Malcolm Crossley <malcolm.crossley@citrix.com>
Subject: Re: [PATCH v2] Xen: Spread boot time page scrubbing across all available	CPU's
Date: Thu, 10 Apr 2014 13:09:50 +0200	[thread overview]
Message-ID: <1397128190.5295.109.camel@Abyss> (raw)
In-Reply-To: <20140409142059.GB5860@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]

On Wed, 2014-04-09 at 10:20 -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Apr 03, 2014 at 11:00:07AM +0200, Tim Deegan wrote:

> An option would be for the worker to do:
> 
> void __init smp_scrub_heap_pages(void *data)
> {
> 	bool_t scrub_bsp = (bool_t)data;
> 	unsigned long node_id = cpu_to_node(smp_processor_id());
> 	struct scrub_region *data;
> 
> 	if (node_id == NUMA_NO_NODE)
> 		if (scrub_bsp)
> 			data = region[0];
> 		else
> 			goto out;
> 	else
> 		data = region[node_id];
> 
> and use that. Then the parameter passed in is just whether this
> is the first loop (false) or the second loop (true).
> 
> 
> Or perhaps:
> 
> >You're struggling a little to force this information into the SMP
> >protocol; I think it would be cleaner if you carved the central loop of
> >smp_scrub_heap_pages() out into its own funciton and called that here
> >instead.
> 
> Just do that and then the workers will just quit if they detect
> (node_id == NUMA_NO_NODE) and there is no parameter parsing.
> 
FWIW, I think this option would look a lot better.

> Let me try that.		
> 
Let us know how it goes... I'm also interested in this patch.

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2014-04-10 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 12:35 [PATCH v2] Xen: Spread boot time page scrubbing across all available CPU's Malcolm Crossley
2013-09-30 13:26 ` Jan Beulich
2013-09-30 13:56   ` Malcolm Crossley
2013-09-30 15:35     ` Jan Beulich
2013-09-30 15:42       ` Andrew Cooper
2013-09-30 16:08         ` Jan Beulich
2013-09-30 17:43 ` Konrad Rzeszutek Wilk
2013-10-03 11:39 ` Tim Deegan
2014-04-01 19:29 ` Konrad Rzeszutek Wilk
2014-04-03  1:19   ` Konrad Rzeszutek Wilk
2014-04-03  8:35     ` Jan Beulich
2014-04-03  9:00     ` Tim Deegan
2014-04-09 14:20       ` Konrad Rzeszutek Wilk
2014-04-10 11:09         ` Dario Faggioli [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=1397128190.5295.109.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@darnok.org \
    --cc=malcolm.crossley@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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.