All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ankit Jain <ankitja@vmware.com>
To: juri.lelli@redhat.com, bristot@redhat.com,
	l.stach@pengutronix.de, suhui_kernel@163.com,
	msimmons@redhat.com, peterz@infradead.org, glenn@aurora.tech,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org
Cc: srivatsab@vmware.com, srivatsa@csail.mit.edu, akaher@vmware.com,
	amakhalov@vmware.com, vsirnapalli@vmware.com,
	sturlapati@vmware.com, bordoloih@vmware.com,
	keerthanak@vmware.com, Ankit Jain <ankitja@vmware.com>
Subject: [PATCH v4.19.y 4/4] kernel/sched: Remove dl_boosted flag comment
Date: Mon, 22 Aug 2022 13:13:48 +0530	[thread overview]
Message-ID: <20220822074348.218135-5-ankitja@vmware.com> (raw)
In-Reply-To: <20220822074348.218135-1-ankitja@vmware.com>

From: Hui Su <suhui_kernel@163.com>

commit 0e3872499de1a1230cef5221607d71aa09264bd5 upstream.

since commit 2279f540ea7d ("sched/deadline: Fix priority
inheritance with multiple scheduling classes"), we should not
keep it here.

Signed-off-by: Hui Su <suhui_kernel@163.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Daniel Bristot de Oliveira <bristot@redhat.com>
Link: https://lore.kernel.org/r/20220107095254.GA49258@localhost.localdomain
[Ankit: Regenerated the patch for v4.19.y]
Signed-off-by: Ankit Jain <ankitja@vmware.com>
---
 include/linux/sched.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/include/linux/sched.h b/include/linux/sched.h
index 2ed820558da1..bc04745da6c1 100644
--- a/include/linux/sched.h
+++ b/include/linux/sched.h
@@ -528,10 +528,6 @@ struct sched_dl_entity {
 	 * task has to wait for a replenishment to be performed at the
 	 * next firing of dl_timer.
 	 *
-	 * @dl_boosted tells if we are boosted due to DI. If so we are
-	 * outside bandwidth enforcement mechanism (but only until we
-	 * exit the critical section);
-	 *
 	 * @dl_yielded tells if task gave up the CPU before consuming
 	 * all its available runtime during the last job.
 	 *
-- 
2.34.1


  parent reply	other threads:[~2022-08-22  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  7:43 [PATCH v4.19.y 0/4] sched/deadline: Fix panic due to nested priority inheritance Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 1/4] sched/deadline: Unthrottle PI boosted threads while enqueuing Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 2/4] sched/deadline: Fix stale throttling on de-/boosted tasks Ankit Jain
2022-08-22  7:43 ` [PATCH v4.19.y 3/4] sched/deadline: Fix priority inheritance with multiple scheduling classes Ankit Jain
2022-08-22  7:43 ` Ankit Jain [this message]
2022-08-25 12:31 ` [PATCH v4.19.y 0/4] sched/deadline: Fix panic due to nested priority inheritance Greg KH

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=20220822074348.218135-5-ankitja@vmware.com \
    --to=ankitja@vmware.com \
    --cc=akaher@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=bordoloih@vmware.com \
    --cc=bristot@redhat.com \
    --cc=glenn@aurora.tech \
    --cc=gregkh@linuxfoundation.org \
    --cc=juri.lelli@redhat.com \
    --cc=keerthanak@vmware.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msimmons@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=stable@vger.kernel.org \
    --cc=sturlapati@vmware.com \
    --cc=suhui_kernel@163.com \
    --cc=vsirnapalli@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.