mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Fernandes <joel@joelfernandes.org>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Aashish Sharma <shraash@google.com>,
	Vineeth Pillai <vineeth@bitbyteword.org>
Subject: Re: [PATCH] sched/deadline: Do not start hrtick if its disabled for DL
Date: Tue, 12 Nov 2024 18:36:36 +0000	[thread overview]
Message-ID: <20241112183636.GB2061573@google.com> (raw)
In-Reply-To: <ZzMI9dYjWKqNtQzv@jlelli-thinkpadt14gen4.remote.csb>

On Tue, Nov 12, 2024 at 07:51:17AM +0000, Juri Lelli wrote:
> Hi Joel,
> 
> On 12/11/24 01:22, Joel Fernandes (Google) wrote:
> > Fix an issue where high-resolution timers causes aggressive preemptions,
> > leading to increased idle times in CFS tasks (which are inside the DL
> > server). The problem was traced to improper usage of hrtick_enabled(),
> > which could start high-resolution ticks unexpectedly causing repeated
> > preemptions.
> > 
> > The fix replaces this call with hrtick_enabled_dl(), aligning it with
> > scheduler feature checks.
> > 
> > Reported-by: Aashish Sharma <shraash@google.com>
> > Reported-by: Vineeth Pillai <vineeth@bitbyteword.org>
> > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > ---
> >  kernel/sched/deadline.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> > index b216e6deeac4..d46502b9ce58 100644
> > --- a/kernel/sched/deadline.c
> > +++ b/kernel/sched/deadline.c
> > @@ -2121,7 +2121,7 @@ static struct task_struct *pick_next_task_dl(struct rq *rq)
> >  	if (!p->dl_server)
> >  		set_next_task_dl(rq, p, true);
> >  
> > -	if (hrtick_enabled(rq))
> > +	if (hrtick_enabled_dl(rq))
> >  		start_hrtick_dl(rq, &p->dl);
> >  
> >  	return p;
> > -- 
> 
> I'm not sure I'm seeing this in current code. We have two users in
> deadline.c and they both use hrtick_enabled_dl (after a recent fix by
> Phil).

Ah you're right. The latest kernel we are on is on 6.6 so this got missed.

Thanks Juri for your quick reply and pointing out the missing patches!

 - Joel


      reply	other threads:[~2024-11-12 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  1:22 Joel Fernandes (Google)
2024-11-12  7:51 ` Juri Lelli
2024-11-12 18:36   ` Joel Fernandes [this message]

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=20241112183636.GB2061573@google.com \
    --to=joel@joelfernandes.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=shraash@google.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vineeth@bitbyteword.org \
    --cc=vschneid@redhat.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

all inboxes | Powered by JetHome®