public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: move some code from macro to function
Date: Sat, 27 Mar 2010 21:15:54 -0700	[thread overview]
Message-ID: <20100328041554.GQ2343@linux.vnet.ibm.com> (raw)
In-Reply-To: <4BAEC91E.8000001@cn.fujitsu.com>

On Sun, Mar 28, 2010 at 11:12:30AM +0800, Lai Jiangshan wrote:
> 
> cleanup: move some code from macro to function

Nice!

I have queued this for RCU 2.6.35, with the following commit message:

	Shrink the RCU_INIT_FLAVOR() macro by moving all but the
	initialization of the ->rda[] array to rcu_init_one().
	The call to rcu_init_one() can then be moved to the end
	of the RCU_INIT_FLAVOR() macro, which is required because
	rcu_boot_init_percpu_data(), which is now called from
	rcu_init_one(), depends on the initialization of the ->rda[]
	array.

Seem reasonable?

							Thanx, Paul

> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/rcutree.c b/kernel/rcutree.c
> index 3ec8160..112edb5 100644
> --- a/kernel/rcutree.c
> +++ b/kernel/rcutree.c
> @@ -1849,6 +1849,14 @@ static void __init rcu_init_one(struct rcu_state *rsp)
>  			INIT_LIST_HEAD(&rnp->blocked_tasks[3]);
>  		}
>  	}
> +
> +	rnp = rsp->level[NUM_RCU_LVLS - 1];
> +	for_each_possible_cpu(i) {
> +		if (i > rnp->grphi)
> +			rnp++;
> +		rsp->rda[i]->mynode = rnp;
> +		rcu_boot_init_percpu_data(i, rsp);
> +	}
>  }
> 
>  /*
> @@ -1859,19 +1867,11 @@ static void __init rcu_init_one(struct rcu_state *rsp)
>  #define RCU_INIT_FLAVOR(rsp, rcu_data) \
>  do { \
>  	int i; \
> -	int j; \
> -	struct rcu_node *rnp; \
>  	\
> -	rcu_init_one(rsp); \
> -	rnp = (rsp)->level[NUM_RCU_LVLS - 1]; \
> -	j = 0; \
>  	for_each_possible_cpu(i) { \
> -		if (i > rnp[j].grphi) \
> -			j++; \
> -		per_cpu(rcu_data, i).mynode = &rnp[j]; \
>  		(rsp)->rda[i] = &per_cpu(rcu_data, i); \
> -		rcu_boot_init_percpu_data(i, rsp); \
>  	} \
> +	rcu_init_one(rsp); \
>  } while (0)
> 
>  void __init rcu_init(void)
> 

  reply	other threads:[~2010-03-28  4:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28  3:12 [PATCH] rcu: move some code from macro to function Lai Jiangshan
2010-03-28  4:15 ` Paul E. McKenney [this message]
2010-03-29  1:03   ` Lai Jiangshan

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=20100328041554.GQ2343@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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