From: Marcelo Tosatti <mtosatti@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Frederic Weisbecker <frederic@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Nitesh Narayan Lal <nitesh@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: [patch 0/2] nohz_full: only wakeup target CPUs when notifying new tick dependency (v2)
Date: Wed, 07 Oct 2020 15:01:51 -0300 [thread overview]
Message-ID: <20201007180151.623061463@redhat.com> (raw)
When enabling per-CPU posix timers, an IPI to nohz_full CPUs might be
performed (to re-read the dependencies and possibly not re-enter
nohz_full on a given CPU).
A common case is for applications that run on nohz_full= CPUs
to not use POSIX timers (eg DPDK). This patch changes the notification
to only IPI the target CPUs where the task(s) whose tick dependencies
are being updated are executing.
This reduces interruptions to nohz_full= CPUs.
next reply other threads:[~2020-10-07 18:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 18:01 Marcelo Tosatti [this message]
2020-10-07 18:01 ` [patch 1/2] nohz: only wakeup a single target cpu when kicking a task Marcelo Tosatti
2020-10-08 12:22 ` Peter Zijlstra
2020-10-08 17:54 ` Marcelo Tosatti
2020-10-08 19:54 ` Frederic Weisbecker
2020-10-13 17:13 ` Marcelo Tosatti
2020-10-14 8:33 ` Peter Zijlstra
2020-10-14 23:40 ` Frederic Weisbecker
2020-10-15 10:12 ` Peter Zijlstra
2020-10-26 14:42 ` Frederic Weisbecker
2020-10-20 18:52 ` Marcelo Tosatti
2020-10-22 12:53 ` Frederic Weisbecker
2020-10-08 14:59 ` Peter Xu
2020-10-08 15:28 ` Peter Zijlstra
2020-10-08 19:16 ` Peter Xu
2020-10-08 19:48 ` Frederic Weisbecker
2020-10-08 17:43 ` Marcelo Tosatti
2020-10-07 18:01 ` [patch 2/2] nohz: change signal tick dependency to wakeup CPUs of member tasks Marcelo Tosatti
2020-10-08 12:35 ` Peter Zijlstra
2020-10-08 18:04 ` Marcelo Tosatti
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=20201007180151.623061463@redhat.com \
--to=mtosatti@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nitesh@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.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).