From: Alexander Gordeev <agordeev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] rcu: Cleanup rcu_init_geometry() code and arithmetics
Date: Wed, 3 Jun 2015 07:37:29 +0100 [thread overview]
Message-ID: <20150603063728.GC3679@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <1433312333-23597-1-git-send-email-agordeev@redhat.com>
On Wed, Jun 03, 2015 at 08:18:32AM +0200, Alexander Gordeev wrote:
> This update simplifies rcu_init_geometry() code flow
> and makes calculation of the total number of rcu_node
> structures more easy to read.
>
> The update relies on the fact num_rcu_lvl[] is never
> accessed beyond rcu_num_lvls index by the rest of the
> code. Therefore, there is no need initialize the whole
> num_rcu_lvl[].
Please, ignore this one.
> Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> ---
> kernel/rcu/tree.c | 24 ++++++++++--------------
> 1 file changed, 10 insertions(+), 14 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index d77b0fb..0e8c24d 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -4038,7 +4038,6 @@ static void __init rcu_init_geometry(void)
> {
> ulong d;
> int i;
> - int j;
> int rcu_capacity[MAX_RCU_LVLS + 1];
>
> /*
> @@ -4089,24 +4088,21 @@ static void __init rcu_init_geometry(void)
> return;
> }
>
> + /* Calculate the number of levels in the tree. */
> + for (i = 1; nr_cpu_ids > rcu_capacity[i]; i++) {
> + }
> + rcu_num_lvls = i;
> +
> /* Calculate the number of rcu_nodes at each level of the tree. */
> - for (i = 1; i <= MAX_RCU_LVLS; i++)
> - if (nr_cpu_ids <= rcu_capacity[i]) {
> - for (j = 0; j <= i; j++) {
> - int cap = rcu_capacity[i - j];
> - num_rcu_lvl[j] = DIV_ROUND_UP(nr_cpu_ids, cap);
> - }
> - rcu_num_lvls = i;
> - for (j = i + 1; j <= MAX_RCU_LVLS; j++)
> - num_rcu_lvl[j] = 0;
> - break;
> - }
> + for (i = 0; i < rcu_num_lvls; i++) {
> + int cap = rcu_capacity[rcu_num_lvls - i];
> + num_rcu_lvl[i] = DIV_ROUND_UP(nr_cpu_ids, cap);
> + }
>
> /* Calculate the total number of rcu_node structures. */
> rcu_num_nodes = 0;
> - for (i = 0; i <= MAX_RCU_LVLS; i++)
> + for (i = 0; i < rcu_num_lvls; i++)
> rcu_num_nodes += num_rcu_lvl[i];
> - rcu_num_nodes -= nr_cpu_ids;
> }
>
> void __init rcu_init(void)
> --
> 1.8.3.1
>
--
Regards,
Alexander Gordeev
agordeev@redhat.com
prev parent reply other threads:[~2015-06-03 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 6:18 Alexander Gordeev
2015-06-03 6:37 ` Alexander Gordeev [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=20150603063728.GC3679@agordeev.usersys.redhat.com \
--to=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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
all inboxes | Powered by JetHome®