LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org> To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org> Cc: LKML <linux-kernel@vger.kernel.org>, Frederic Weisbecker <frederic@kernel.org>, Peter Zijlstra <peterz@infradead.org>, "Eric W . Biederman" <ebiederm@xmission.com>, Oleg Nesterov <oleg@redhat.com> Subject: [GIT PULL] posix-cpu-timers leftover overhead fixes Date: Mon, 26 Jul 2021 14:55:07 +0200 [thread overview] Message-ID: <20210726125513.271824-1-frederic@kernel.org> (raw) Thomas, Ingo, Please pull the timers/core branch that can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git timers/core HEAD: 63a17eea7d5516f9e927fdc52b45f1d040fdcf35 --- Those are not regression fixes since these bugs precede the git-era, therefore they are not carrying a stable tag. Several posix cpu timers events (setting, deletion, expiration) may end up leaving needless elapsing overhead after a timer has stopped or even after it has been deleted. Those overhead are: 1) Costly process wide cputime accounting that rely on concurrent atomic addition during tick or even more frequent scheduler internal stat updates. 2) Retained tick dependency on NOHZ_FULL configurations. Hopefully this series gets rid of all the possible culprits. Thanks, Frederic --- Frederic Weisbecker (6): posix-cpu-timers: Assert task sighand is locked while starting cputime counter posix-cpu-timers: Force next_expiration recalc after timer deletion posix-cpu-timers: Force next expiration recalc after itimer reset posix-cpu-timers: Remove confusing error code override posix-cpu-timers: Consolidate timer base accessor posix-cpu-timers: Recalc next expiration when timer_settime() ends up not queueing include/linux/posix-timers.h | 11 +++++- include/linux/sched/signal.h | 6 +++ kernel/signal.c | 15 +++++++ kernel/time/posix-cpu-timers.c | 90 ++++++++++++++++++++++++++++++++++-------- 4 files changed, 103 insertions(+), 19 deletions(-)
next reply other threads:[~2021-07-26 12:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-26 12:55 Frederic Weisbecker [this message] 2021-07-26 12:55 ` [PATCH 1/6] posix-cpu-timers: Assert task sighand is locked while starting cputime counter Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker 2021-07-26 12:55 ` [PATCH 2/6] posix-cpu-timers: Force next_expiration recalc after timer deletion Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker 2021-07-26 12:55 ` [PATCH 3/6] posix-cpu-timers: Force next expiration recalc after itimer reset Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker 2021-07-26 12:55 ` [PATCH 4/6] posix-cpu-timers: Remove confusing error code override Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] posix-cpu-timers: Remove confusing return value override tip-bot2 for Frederic Weisbecker 2021-07-26 12:55 ` [PATCH 5/6] posix-cpu-timers: Consolidate timer base accessor Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker 2021-07-26 12:55 ` [PATCH 6/6] posix-cpu-timers: Recalc next expiration when timer_settime() ends up not queueing Frederic Weisbecker 2021-08-10 15:13 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
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=20210726125513.271824-1-frederic@kernel.org \ --to=frederic@kernel.org \ --cc=ebiederm@xmission.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=oleg@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: linkBe 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).