mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prasad Sodagudi <psodagud@codeaurora.org>
To: john.stultz@linaro.org, tglx@linutronix.de, sboyd@kernel.org
Cc: linux-kernel@vger.kernel.org, saravanak@google.com,
	tsoni@codeaurora.org, tj@kernel.org,
	Prasad Sodagudi <psodagud@codeaurora.org>
Subject: [PATCH 0/2] timer: make deferrable cpu unbound timers really not bound to a cpu
Date: Sun, 15 Mar 2020 19:39:08 -0700	[thread overview]
Message-ID: <1584326350-30275-1-git-send-email-psodagud@codeaurora.org> (raw)


These patches introduce support for global deferrable timers and this feature is very useful
for the mobile chipsets. There was a discussion on global deferrable timer discussion - [1]
and thomas raised cacheline bouncing problem. I am thinking that, that problem is addressed
on later patches problem as much as possible. Global deferrable timers runs on the
tick_do_timer_cpu to avoid cacheline bouncing problem during the execution of timers.  

[1]- https://lore.kernel.org/patchwork/patch/500541/


Joonwoo Park (1):
  timer: make deferrable cpu unbound timers really not bound to a cpu

Prasad Sodagudi (1):
  sched: Add a check for cpu unbound deferrable timers

 include/linux/timer.h    |  3 +++
 kernel/time/tick-sched.c |  6 +++++
 kernel/time/timer.c      | 63 ++++++++++++++++++++++++++++++++++++++++++++----
 3 files changed, 67 insertions(+), 5 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2020-03-16  2:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  2:39 Prasad Sodagudi [this message]
2020-03-16  2:39 ` [PATCH 1/2] " Prasad Sodagudi
2020-03-16  2:39 ` [PATCH 2/2] sched: Add a check for cpu unbound deferrable timers Prasad Sodagudi
2020-03-16  8:38   ` Thomas Gleixner
2020-03-16 11:27   ` Pavan Kondeti

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=1584326350-30275-1-git-send-email-psodagud@codeaurora.org \
    --to=psodagud@codeaurora.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@google.com \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=tsoni@codeaurora.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

Powered by JetHome