From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien.grall@arm.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 3/3] xen: RCU: make the period of the idle timer adaptive.
Date: Tue, 26 Sep 2017 19:50:50 +0200 [thread overview]
Message-ID: <1506448250.27663.36.camel@citrix.com> (raw)
In-Reply-To: <59CA8D5C020000780017FE08@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1473 bytes --]
On Tue, 2017-09-26 at 09:24 -0600, Jan Beulich wrote:
> > > > On 15.09.17 at 20:01, <dario.faggioli@citrix.com> wrote:
> > @@ -495,8 +507,18 @@ void rcu_idle_timer_stop()
> >
> > static void rcu_idle_timer_handler(void* data)
> > {
> > - /* Nothing, really... Just count the number of times we fire
> > */
> > perfc_incr(rcu_idle_timer);
> > +
> > + if ( !cpumask_empty(&rcu_ctrlblk.cpumask) )
> > + {
> > + idle_timer_period = min_t(s_time_t, IDLE_TIMER_PERIOD_MAX,
> > + idle_timer_period +
> > IDLE_TIMER_PERIOD_INCR);
> > + }
> > + else
> > + {
> > + idle_timer_period = max_t(s_time_t, IDLE_TIMER_PERIOD_MIN,
> > + idle_timer_period -
> > IDLE_TIMER_PERIOD_DECR);
> > + }
>
> Pointless braces. And do you really need min_t()/max_t() here,
> rather than just min()/max()?
>
I probably can. This must be a leftover from a version when the time of
idle_timer_period, and of the IDLE_TIMER_PERIOD_{MIN,MAX} constants
wasn't matching.
Sorry!
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-26 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 18:01 [PATCH 0/3] xen: RCU: Improve the idle timer handling Dario Faggioli
2017-09-15 18:01 ` [PATCH 1/3] xen: timers: don't miss a timer event because of stop_timer() Dario Faggioli
2017-09-26 14:59 ` Jan Beulich
2017-09-26 18:11 ` Dario Faggioli
2017-09-27 8:20 ` Jan Beulich
2017-09-27 10:18 ` Dario Faggioli
2017-09-27 10:30 ` Jan Beulich
2017-09-27 13:39 ` Dario Faggioli
2017-09-28 9:51 ` Dario Faggioli
2017-09-15 18:01 ` [PATCH 2/3] xen: RCU: make the period of the idle timer configurable Dario Faggioli
2017-09-26 15:14 ` Jan Beulich
2017-09-26 17:48 ` Dario Faggioli
2017-09-27 8:26 ` Jan Beulich
2017-09-15 18:01 ` [PATCH 3/3] xen: RCU: make the period of the idle timer adaptive Dario Faggioli
2017-09-26 15:24 ` Jan Beulich
2017-09-26 17:50 ` Dario Faggioli [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=1506448250.27663.36.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).