From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Sebastien Laveze <sebastien.laveze@oss.nxp.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: timerfd performances
Date: Fri, 22 Jan 2021 13:30:57 +0100 [thread overview]
Message-ID: <20210122123057.72aeag672rh3omcw@linutronix.de> (raw)
In-Reply-To: <e4c83482f22059647c546f202470d05e142134bc.camel@oss.nxp.com>
On 2021-01-18 17:10:15 [+0100], Sebastien Laveze wrote:
> Hi,
Hi,
> In the end, it seems my most viable option at the moment is to move to
> clock_nanosleep() but it implies radical changes in my application
> architecture as it's not as scalable and flexible as timerfd.
>
> Any hints on how to "secure" the wake-up latency of timer fds or what
> is expected in future works would be greatly appreciated !
Splitting the timer-wakeups back into ktimersoftd would look like
helping. But note that all timer wake ups would happen there - even the
accumulated case where we have to wake 100 tasks at once. This would
then probably ask for split on SCHED_OTHER vs RT tasks like it is done
for clock_nanosleep().
> Thanks,
> Seb
Sebastian
next prev parent reply other threads:[~2021-01-22 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 16:10 timerfd performances Sebastien Laveze
2021-01-22 12:30 ` Sebastian Andrzej Siewior [this message]
2021-01-22 13:23 ` Sebastien Laveze
2021-01-22 14:07 ` 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=20210122123057.72aeag672rh3omcw@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=sebastien.laveze@oss.nxp.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).