From: Tom Rix <trix@redhat.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
dietmar.eggemann@arm.com, bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org
Subject: [PATCH] sched: remove noop function task_fork_dl
Date: Wed, 27 Nov 2019 09:03:28 -0800 [thread overview]
Message-ID: <56b066c2-90fd-4263-cf31-0a08ea44fd53@redhat.com> (raw)
task_fork_dl is an empty function used only for dl's
sched_class.task_fork. Removing it cleans up the code a bit
and saves a function call in sched_fork.
Signed-off-by: Tom Rix <trix@redhat.com>
---
kernel/sched/deadline.c | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index a8a08030a8f7..fbafd97d883a 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -1821,14 +1821,6 @@ static void task_tick_dl(struct rq *rq, struct task_struct *p, int queued)
start_hrtick_dl(rq, p);
}
-static void task_fork_dl(struct task_struct *p)
-{
- /*
- * SCHED_DEADLINE tasks cannot fork and this is achieved through
- * sched_fork()
- */
-}
-
#ifdef CONFIG_SMP
/* Only try algorithms three times */
@@ -2451,8 +2443,6 @@ const struct sched_class dl_sched_class = {
#endif
.task_tick = task_tick_dl,
- .task_fork = task_fork_dl,
-
.prio_changed = prio_changed_dl,
.switched_from = switched_from_dl,
.switched_to = switched_to_dl,
--
2.23.0
next reply other threads:[~2019-11-27 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 17:03 Tom Rix [this message]
2019-11-29 7:13 ` [PATCH] sched: remove noop function task_fork_dl Ingo Molnar
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=56b066c2-90fd-4263-cf31-0a08ea44fd53@redhat.com \
--to=trix@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=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;
as well as URLs for NNTP newsgroup(s).