From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Josh Triplett <josht@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [PATCH 3/4] rcu: Add rcu_bh_sync torture type to rcutorture
Date: Thu, 31 Aug 2006 18:30:00 -0700 [thread overview]
Message-ID: <20060901013000.GF4927@us.ibm.com> (raw)
In-Reply-To: <1157065016.25808.8.camel@josh-work.beaverton.ibm.com>
On Thu, Aug 31, 2006 at 03:56:56PM -0700, Josh Triplett wrote:
> Use the newly-generic synchronous deferred free function to implement torture
> testing for rcu_bh using synchronize_rcu_bh rather than the asynchronous
> call_rcu_bh.
Acked-by: Paul E. McKenney <paulmck@us.ibm.com>
> Signed-off-by: Josh Triplett <josh@freedesktop.org>
> ---
> Documentation/RCU/torture.txt | 5 +++--
> kernel/rcutorture.c | 16 +++++++++++++++-
> 2 files changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/RCU/torture.txt b/Documentation/RCU/torture.txt
> index 6714b53..cc4b1ef 100644
> --- a/Documentation/RCU/torture.txt
> +++ b/Documentation/RCU/torture.txt
> @@ -55,8 +55,9 @@ test_no_idle_hz Whether or not to test t
>
> torture_type The type of RCU to test: "rcu" for the rcu_read_lock() API,
> "rcu_sync" for rcu_read_lock() with synchronous reclamation,
> - "rcu_bh" for the rcu_read_lock_bh() API, and "srcu" for the
> - "srcu_read_lock()" API.
> + "rcu_bh" for the rcu_read_lock_bh() API, "rcu_bh_sync" for
> + rcu_read_lock_bh() with synchronous reclamation, and "srcu"
> + for the "srcu_read_lock()" API.
>
> verbose Enable debug printk()s. Default is disabled.
>
> diff --git a/kernel/rcutorture.c b/kernel/rcutorture.c
> index 1c329df..0f0ff15 100644
> --- a/kernel/rcutorture.c
> +++ b/kernel/rcutorture.c
> @@ -370,6 +370,19 @@ static struct rcu_torture_ops rcu_bh_ops
> .name = "rcu_bh"
> };
>
> +static struct rcu_torture_ops rcu_bh_sync_ops = {
> + .init = rcu_sync_torture_init,
> + .cleanup = NULL,
> + .readlock = rcu_bh_torture_read_lock,
> + .readdelay = rcu_read_delay, /* just reuse rcu's version. */
> + .readunlock = rcu_bh_torture_read_unlock,
> + .completed = rcu_bh_torture_completed,
> + .deferredfree = rcu_sync_torture_deferred_free,
> + .sync = rcu_bh_torture_synchronize,
> + .stats = NULL,
> + .name = "rcu_bh_sync"
> +};
> +
> /*
> * Definitions for srcu torture testing.
> */
> @@ -452,7 +465,8 @@ static struct rcu_torture_ops srcu_ops =
> };
>
> static struct rcu_torture_ops *torture_ops[] =
> - { &rcu_ops, &rcu_sync_ops, &rcu_bh_ops, &srcu_ops, NULL };
> + { &rcu_ops, &rcu_sync_ops, &rcu_bh_ops, &rcu_bh_sync_ops, &srcu_ops,
> + NULL };
>
> /*
> * RCU torture writer kthread. Repeatedly substitutes a new structure
> --
> 1.4.1.1
>
>
prev parent reply other threads:[~2006-09-01 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 22:56 [PATCH 3/4] rcu: Add rcu_bh_sync torture type to rcutorture Josh Triplett
2006-09-01 1:30 ` Paul E. McKenney [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=20060901013000.GF4927@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=josht@us.ibm.com \
--cc=linux-kernel@vger.kernel.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.