From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
rusty@au1.ibm.com, bmark@us.ibm.com,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC,PATCH] Use RCU to protect tasklist for unicast signals
Date: Thu, 11 Aug 2005 07:14:41 -0700 [thread overview]
Message-ID: <20050811141441.GB1300@us.ibm.com> (raw)
In-Reply-To: <20050811095634.GA19342@elte.hu>
On Thu, Aug 11, 2005 at 11:56:34AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@us.ibm.com> wrote:
>
> > Hello!
> >
> > This patch is an experiment in use of RCU for individual code paths
> > that read-acquire the tasklist lock, in this case, unicast signal
> > delivery. It passes five kernbenches on 4-CPU x86, but obviously needs
> > much more testing before it is considered for serious use, let alone
> > inclusion.
> >
> > My main question is whether I have the POSIX semantics covered. I
> > believe that I do, but thought I should check with people who are more
> > familiar with POSIX than am I.
> >
> > For the record, some shortcomings of this patch:
> >
> > o Needs lots more testing on more architectures.
> >
> > o Needs performance and stress testing.
> >
> > o Needs testing in Ingo's PREEMPT_RT environment.
>
> cool patch! I have integrated it into my PREEMPT_RT tree, and all it
> needed to boot was the patch below (doesnt affect the upstream kernel).
> Using the raw IRQ flag isnt an issue in the RCU code, all the affected
> codepaths are small and deterministic.
>
> (without this patch it locked up after detecting IRQ7 - not sure why.)
Without this patch on an older version of PREEMPT_RT (V0.7.52-12),
it would boot, pass kernbench, but fail LTP. Passed both on a stock
kernel.
Will re-run with your patch. ;-)
> kernel still works fine after some (mostly light) testing.
Cool! Next step for me is to run some focussed stress tests.
Thanx, Paul
> Ingo
>
> Index: linux/kernel/rcupdate.c
> ===================================================================
> --- linux.orig/kernel/rcupdate.c
> +++ linux/kernel/rcupdate.c
> @@ -134,11 +134,11 @@ void fastcall call_rcu(struct rcu_head *
>
> head->func = func;
> head->next = NULL;
> - local_irq_save(flags);
> + raw_local_irq_save(flags);
> rdp = &__get_cpu_var(rcu_data);
> *rdp->nxttail = head;
> rdp->nxttail = &head->next;
> - local_irq_restore(flags);
> + raw_local_irq_restore(flags);
> }
>
> /**
> @@ -165,11 +165,11 @@ void fastcall call_rcu_bh(struct rcu_hea
>
> head->func = func;
> head->next = NULL;
> - local_irq_save(flags);
> + raw_local_irq_save(flags);
> rdp = &__get_cpu_var(rcu_bh_data);
> *rdp->nxttail = head;
> rdp->nxttail = &head->next;
> - local_irq_restore(flags);
> + raw_local_irq_restore(flags);
> }
>
> /*
> @@ -305,11 +305,11 @@ static void rcu_check_quiescent_state(st
> static void rcu_move_batch(struct rcu_data *this_rdp, struct rcu_head *list,
> struct rcu_head **tail)
> {
> - local_irq_disable();
> + raw_local_irq_disable();
> *this_rdp->nxttail = list;
> if (list)
> this_rdp->nxttail = tail;
> - local_irq_enable();
> + raw_local_irq_enable();
> }
>
> static void __rcu_offline_cpu(struct rcu_data *this_rdp,
> @@ -362,13 +362,13 @@ static void __rcu_process_callbacks(stru
> rdp->curtail = &rdp->curlist;
> }
>
> - local_irq_disable();
> + raw_local_irq_disable();
> if (rdp->nxtlist && !rdp->curlist) {
> rdp->curlist = rdp->nxtlist;
> rdp->curtail = rdp->nxttail;
> rdp->nxtlist = NULL;
> rdp->nxttail = &rdp->nxtlist;
> - local_irq_enable();
> + raw_local_irq_enable();
>
> /*
> * start the next batch of callbacks
> @@ -388,7 +388,7 @@ static void __rcu_process_callbacks(stru
> spin_unlock(&rsp->lock);
> }
> } else {
> - local_irq_enable();
> + raw_local_irq_enable();
> }
> rcu_check_quiescent_state(rcp, rsp, rdp);
> if (rdp->donelist)
>
next prev parent reply other threads:[~2005-08-11 14:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 17:11 [RFC,PATCH] Use RCU to protect tasklist for unicast signals Paul E. McKenney
2005-08-11 9:56 ` Ingo Molnar
2005-08-11 14:14 ` Paul E. McKenney [this message]
2005-08-12 2:00 ` Lee Revell
2005-08-12 6:36 ` Ingo Molnar
2005-08-12 20:57 ` Paul E. McKenney
2005-08-11 17:14 ` Christoph Hellwig
2005-08-11 17:56 ` Paul E. McKenney
2005-08-11 18:00 ` Dipankar Sarma
2005-08-11 18:12 ` Dipankar Sarma
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 12:16 Oleg Nesterov
2005-08-11 15:20 ` Paul E. McKenney
2005-08-12 1:56 ` Paul E. McKenney
2005-08-12 8:51 ` Oleg Nesterov
2005-08-12 15:42 ` Paul E. McKenney
2005-08-15 17:44 ` Paul E. McKenney
2005-08-16 8:14 ` Ingo Molnar
2005-08-16 11:56 ` Oleg Nesterov
2005-08-16 17:07 ` Paul E. McKenney
2005-08-17 1:48 ` Paul E. McKenney
2005-08-17 6:35 ` Ingo Molnar
2005-08-17 14:35 ` Oleg Nesterov
2005-08-17 21:19 ` Paul E. McKenney
2005-08-18 11:48 ` Oleg Nesterov
2005-08-19 1:29 ` Paul E. McKenney
2005-08-19 13:27 ` Oleg Nesterov
2005-08-19 18:34 ` Paul E. McKenney
2005-08-18 12:24 ` Oleg Nesterov
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=20050811141441.GB1300@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=akpm@osdl.org \
--cc=bmark@us.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@au1.ibm.com \
--cc=tglx@linutronix.de \
/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