From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Nicolas Saenz Julienne <nsaenzju@redhat.com>,
linux-rt-users@vger.kernel.org, frederic@kernel.org,
mtosatti@redhat.com, LKML <linux-kernel@vger.kernel.org>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [RFC 2/2] timers: Make sure irq_work is handled when no pending timers
Date: Tue, 22 Jun 2021 19:42:54 +0200 [thread overview]
Message-ID: <YNIhHmAekp2sUBCN@krava> (raw)
In-Reply-To: <YNIe38WaY0lOTEAZ@krava>
On Tue, Jun 22, 2021 at 07:33:23PM +0200, Jiri Olsa wrote:
> On Tue, Jun 22, 2021 at 03:44:23PM +0200, Peter Zijlstra wrote:
> > On Sat, Jun 19, 2021 at 12:47:04AM +0200, Thomas Gleixner wrote:
> > > There are two solutions:
> > >
> > > 1) Create a IRQ_WORK softirq and raise that
> > >
> > > 2) Simply delegate it to a workqueue
> >
> > IIRC someone was looking to stick the whole thing in a kthread_worker.
> > Jiri, was that you?
> >
>
> yep, I still plan on doing that
hum, IIRC that was actually perf specific change we discussed some
time ago I should have read the whole thread before answering
I'll check what was my plan to do and get back ;-)
jirka
next prev parent reply other threads:[~2021-06-22 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:59 [RFC 1/2] timers: Add pending timer bool in struct timer_base Nicolas Saenz Julienne
2021-06-10 12:59 ` [RFC 2/2] timers: Make sure irq_work is handled when no pending timers Nicolas Saenz Julienne
2021-06-18 22:47 ` Thomas Gleixner
2021-06-19 8:22 ` Thomas Gleixner
2021-06-22 13:44 ` Peter Zijlstra
2021-06-22 17:33 ` Jiri Olsa
2021-06-22 17:42 ` Jiri Olsa [this message]
2021-06-30 17:43 ` Alison Chaiken
2021-06-18 21:06 ` [RFC 1/2] timers: Add pending timer bool in struct timer_base Thomas Gleixner
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=YNIhHmAekp2sUBCN@krava \
--to=jolsa@redhat.com \
--cc=frederic@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).