xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com,
	george.dunlap@eu.citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, JBeulich@suse.com
Subject: Re: [PATCH] numa.c: convert to xen coding style
Date: Thu, 4 Sep 2014 12:43:29 +0200	[thread overview]
Message-ID: <1409827409.2673.161.camel@Solace.lan> (raw)
In-Reply-To: <1409803484-15839-1-git-send-email-ufimtseva@gmail.com>


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

On gio, 2014-09-04 at 00:04 -0400, Elena Ufimtseva wrote:
> Convert to Xen coding style from mixed one.
> 
Ah... Much better, thanks Elena for doing this! :-)

I only have one nit.

> --- a/xen/arch/x86/numa.c
> +++ b/xen/arch/x86/numa.c

>  void __init numa_init_array(void)
>  {
> -	int rr, i;
> -	/* There are unfortunately some poorly designed mainboards around
> -	   that only connect memory to a single CPU. This breaks the 1:1 cpu->node
> -	   mapping. To avoid this fill in the mapping for all possible
> -	   CPUs, as the number of CPUs is not known yet. 
> -	   We round robin the existing nodes. */
> -	rr = first_node(node_online_map);
> -	for (i = 0; i < nr_cpu_ids; i++) {
> -		if (cpu_to_node[i] != NUMA_NO_NODE)
> -			continue;
> - 		numa_set_node(i, rr);
> -		rr = next_node(rr, node_online_map);
> -		if (rr == MAX_NUMNODES)
> -			rr = first_node(node_online_map);
> -	}
> -
> +    int rr, i;
> +    /* There are unfortunately some poorly designed mainboards around
> +       that only connect memory to a single CPU. This breaks the 1:1 cpu->node
> +       mapping. To avoid this fill in the mapping for all possible
> +       CPUs, as the number of CPUs is not known yet.
> +       We round robin the existing nodes. */
>
We are not super consistent when it comes to code comments, but I think
this should have become something like this:

/*
 * Example, multi-line comment block.
 *
 * Note beginning and end markers on separate lines and leading '*'.
 */

With this fixed,

Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>

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: 181 bytes --]

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

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  4:04 [PATCH] numa.c: convert to xen coding style Elena Ufimtseva
2014-09-04  4:23 ` Elena Ufimtseva
2014-09-04 10:43 ` Dario Faggioli [this message]
2014-09-04 13:00   ` Elena Ufimtseva
2014-09-04 14:32     ` Jan Beulich
2014-09-04 14:33       ` Elena Ufimtseva
2014-09-04 14:48       ` Dario Faggioli

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=1409827409.2673.161.camel@Solace.lan \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=ufimtseva@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).