From: Alexander Gordeev <agordeev@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Remove redundant rcu_is_cpu_rrupt_from_idle() function
Date: Wed, 29 Oct 2014 13:45:19 +0000 [thread overview]
Message-ID: <20141029134519.GC30198@agordeev.usersys.redhat.com> (raw)
In-Reply-To: <20141029124728.GL5718@linux.vnet.ibm.com>
On Wed, Oct 29, 2014 at 05:47:29AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 29, 2014 at 12:07:07PM +0100, Alexander Gordeev wrote:
> > Function rcu_is_cpu_rrupt_from_idle() is called from scheduling-
> > clock interrupt handler to check if the current CPU was interrupted
> > from idle. If true, it results in invocation of RCU callbacks. But
> > the common hardware interrupt exit path also contains similar check
> > and therefore the call to rcu_is_cpu_rrupt_from_idle() is redundant.
>
> By common hardware interrupt exit path, you are meaning the calls
> to rcu_irq_exit()? If not, please let me know exactly what you
> mean here.
Yes, I mean rcu_irq_exit().
> Thanx, Paul
--
Regards,
Alexander Gordeev
agordeev@redhat.com
next prev parent reply other threads:[~2014-10-29 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 11:07 Alexander Gordeev
2014-10-29 12:47 ` Paul E. McKenney
2014-10-29 13:45 ` Alexander Gordeev [this message]
2014-10-29 14:34 ` Paul E. McKenney
2014-10-29 15:16 ` Alexander Gordeev
2014-10-29 15:46 ` Paul E. McKenney
2014-10-29 21:09 ` Alexander Gordeev
2014-10-30 0:05 ` Paul E. McKenney
2014-10-30 17:54 ` Alexander Gordeev
2014-10-30 20:43 ` Paul E. McKenney
2014-10-30 21:54 ` Alexander Gordeev
2014-10-31 3:45 ` Paul E. McKenney
2014-10-31 14:53 ` Alexander Gordeev
2014-10-31 14:55 ` [PATCH v2] rcu: Remove redundant rcu_is_cpu_rrupt_from_idle() from tiny RCU Alexander Gordeev
2014-10-31 17:36 ` Paul E. McKenney
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=20141029134519.GC30198@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
Powered by JetHome