mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/9] rcu: Cleanup rcu_init_geometry() code and arithmetics
Date: Sat, 7 Mar 2015 18:59:54 +0000	[thread overview]
Message-ID: <20150307185954.GB15033@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <20150307180821.GN5236@linux.vnet.ibm.com>

On Sat, Mar 07, 2015 at 10:08:21AM -0800, Paul E. McKenney wrote:
> The rest of this series looks promising, but I do have to ask...  How have
> you tested these?  The most straightforward approach would be to find

I tried trees with 1,2 and 3 levels on a 160-CPU machine + dozens of kernel
builds with 'make -j160'. I feel bit guilty I did not try the corner case
with 4 levels, but run-time-wise it is not really differ from what I done.

Do you expect the below is a better option?

> a KVM-capable system with at least 16 CPUs and type the following from
> the top-level directory:
> 
> sh tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 34 --duration 5
> 
> This will do a series of 16 build-boot-test cycles with various configs
> (including various rcu_node tree shapes), and print a summary of the
> outcome at the end.
> 
> For these sorts of changes, I usually also do some user-level testing.


-- 
Regards,
Alexander Gordeev
agordeev@redhat.com

  reply	other threads:[~2015-03-07 18:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 17:03 [PATCH 0/9] rcu: Cleanup RCU tree initialization Alexander Gordeev
2015-03-07 17:03 ` [PATCH 1/9] rcu: Panic if RCU tree can not accommodate all CPUs Alexander Gordeev
2015-03-07 17:42   ` Paul E. McKenney
2015-03-07 18:48     ` Alexander Gordeev
2015-03-07 21:52       ` Paul E. McKenney
2015-03-07 17:03 ` [PATCH 2/9] rcu: Remove superfluous local variable in rcu_init_geometry() Alexander Gordeev
2015-03-07 18:03   ` Paul E. McKenney
2015-03-07 17:03 ` [PATCH 3/9] rcu: Cleanup rcu_init_geometry() code and arithmetics Alexander Gordeev
2015-03-07 18:08   ` Paul E. McKenney
2015-03-07 18:59     ` Alexander Gordeev [this message]
2015-03-07 21:47       ` Paul E. McKenney
2015-03-07 17:03 ` [PATCH 4/9] rcu: Simplify rcu_init_geometry() capacity arithmetics Alexander Gordeev
2015-03-07 17:03 ` [PATCH 5/9] rcu: Limit rcu_state::levelcnt[] to RCU_NUM_LVLS items Alexander Gordeev
2015-03-07 17:03 ` [PATCH 6/9] rcu: Limit rcu_capacity[] size " Alexander Gordeev
2015-03-07 17:03 ` [PATCH 7/9] rcu: Remove unnecessary fields from rcu_state structure Alexander Gordeev
2015-03-07 17:03 ` [PATCH 8/9] rcu: Limit count of static data to the number of RCU levels Alexander Gordeev
2015-03-07 17:03 ` [PATCH 9/9] rcu: Simplify arithmetic to calculate number of RCU nodes Alexander Gordeev

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=20150307185954.GB15033@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®