From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: tglx@linutronix.de, linux-rt-users@vger.kernel.org,
peterz@infradead.org, linux-kernel@vger.kernel.org,
bristot@redhat.com, williams@redhat.com
Subject: Re: [RFC PATCH RT 0/2] Add PINNED_HARD mode to hrtimers
Date: Wed, 20 Feb 2019 16:30:56 +0100 [thread overview]
Message-ID: <20190220153055.dt7vm47c2auove3d@linutronix.de> (raw)
In-Reply-To: <20190220074751.GJ21785@localhost.localdomain>
On 2019-02-20 08:47:51 [+0100], Juri Lelli wrote:
> > In this case you prepare the wakeup and then wake the CPU anyway. There
> > should be no downside to this unless the housekeeping CPU is busy and in
> > irq-off regions which would increase the latency. Also in case of
> > cyclictest -d0
> >
> > the one CPU would have to process all timers. So the latency will be
> > worse compared to every CPU does its own wakeup. And on RT you probably
> > do not want to do deep idle anyway.
>
> Mmm, right. But, still very much dependent on the workload, I understand
> you are saying? So, no one size fits all solution.
Now that I slept over it, I think it makes sense from RT point of view
to always pin the timer. I'm not sure if we want to swap the sysctl or
make the PINNED change like you suggested.
> Thanks,
>
> - Juri
Sebastian
next prev parent reply other threads:[~2019-02-20 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 13:37 [RFC PATCH RT 0/2] Add PINNED_HARD mode to hrtimers Juri Lelli
2019-02-14 13:37 ` [RFC PATCH RT 1/2] time/hrtimer: Add PINNED_HARD mode for realtime hrtimers Juri Lelli
2019-02-14 13:37 ` [RFC PATCH RT 2/2] time/hrtimer: Embed hrtimer mode into hrtimer_sleeper Juri Lelli
2019-02-19 17:19 ` [RFC PATCH RT 0/2] Add PINNED_HARD mode to hrtimers Sebastian Andrzej Siewior
2019-02-20 7:47 ` Juri Lelli
2019-02-20 15:30 ` Sebastian Andrzej Siewior [this message]
2019-02-21 8:46 ` Juri Lelli
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=20190220153055.dt7vm47c2auove3d@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).