From: Alison Chaiken <achaiken@aurora.tech>
To: linux-rt-users@vger.kernel.org
Subject: remove of ktimersoftd in linux-rt-devel 5.0
Date: Fri, 15 May 2020 16:46:48 -0700 [thread overview]
Message-ID: <CAFzL-7tzwnBEnt_q2f0BPSAO3To_Zaxt4bLtfzKVOiyJTua45g@mail.gmail.com> (raw)
About a year ago the following commit greatly simplified softirqs:
commit 6f6ba7715a91877cf5fd2b357db3799baa331d9b
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Date: Wed May 29 18:47:32 2019 +0200
softirq: rework
It also removed ktimersoftd, without comment as far as I can see. Is
it obvious that performance improvements due to lockless
synchronization render useless the earlier split of ktimersoftd from
ksoftirqd? Is it now less likely that a large number of other
softirqs that are run immediately when hard IRQs terminate will use up
ksoftirqd's time slice and prevent the timer softirqs from getting a
chance to run?
Thanks,
Alison Chaiken
achaiken@aurora.tech
Aurora Innovation
next reply other threads:[~2020-05-15 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 23:46 Alison Chaiken [this message]
2020-05-26 14:24 ` remove of ktimersoftd in linux-rt-devel 5.0 Sebastian Andrzej Siewior
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=CAFzL-7tzwnBEnt_q2f0BPSAO3To_Zaxt4bLtfzKVOiyJTua45g@mail.gmail.com \
--to=achaiken@aurora.tech \
--cc=linux-rt-users@vger.kernel.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).