mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Tang <tangsong8264@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] sched: Remove unused parameter from update_deadline()
Date: Tue, 15 Oct 2024 21:38:48 +0800	[thread overview]
Message-ID: <c94702d2-c5db-42b3-9ff8-746be98ec2a7@gmail.com> (raw)


After commit 85e511df3cec ("sched/eevdf: Allow shorter slices
to wakeup-preempt"), the 'cfs_rq' argument is no longer used
in update_deadline(). Remove it.

Signed-off-by: Benjamin Tang <tangsong8264@gmail.com>
---
  kernel/sched/fair.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index d9c33f6c1d54..882802d79720 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -1004,7 +1004,7 @@ static void clear_buddies(struct cfs_rq *cfs_rq, 
struct sched_entity *se);
   * XXX: strictly: vd_i += N*r_i/w_i such that: vd_i > ve_i
   * this is probably good enough.
   */
-static bool update_deadline(struct cfs_rq *cfs_rq, struct sched_entity *se)
+static bool update_deadline(struct sched_entity *se)
  {
     if ((s64)(se->vruntime - se->deadline) < 0)
         return false;
@@ -1228,7 +1228,7 @@ static void update_curr(struct cfs_rq *cfs_rq)
         return;

     curr->vruntime += calc_delta_fair(delta_exec, curr);
-   resched = update_deadline(cfs_rq, curr);
+   resched = update_deadline(curr);
     update_min_vruntime(cfs_rq);

     if (entity_is_task(curr)) {
--
2.11.0

             reply	other threads:[~2024-10-15 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 13:38 Benjamin Tang [this message]
2024-10-28  8:39 ` Madadi Vineeth Reddy

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=c94702d2-c5db-42b3-9ff8-746be98ec2a7@gmail.com \
    --to=tangsong8264@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=vincent.guittot@linaro.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

all inboxes | Powered by JetHome®