From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, peterz@infradead.org, yu.c.chen@intel.com,
dietmar.eggemann@arm.com, linux-kernel@vger.kernel.org,
nysal@linux.ibm.com, aboorvad@linux.ibm.com,
srikar@linux.ibm.com, vschneid@redhat.com,
pierre.gondois@arm.com, qyousef@layalina.io
Subject: Re: [PATCH v5 1/3] sched/fair: Add EAS checks before updating overutilized
Date: Thu, 7 Mar 2024 10:20:56 +0530 [thread overview]
Message-ID: <61ef7ebd-f5cf-4d48-9bbd-f011d751041a@linux.ibm.com> (raw)
In-Reply-To: <CAKfTPtCnN95A8kQ-uBA7ykTMAzQVRzwER-XNJt4YyQXdxhDCTQ@mail.gmail.com>
On 3/6/24 11:10 PM, Vincent Guittot wrote:
> On Wed, 6 Mar 2024 at 11:25, Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
>> #else
>> -static inline void update_overutilized_status(struct rq *rq) { }
>> +static inline void check_update_overutilized_status(struct rq *rq)
>> +{
>> + return 0;
>> +}
>
> static inline void check_update_overutilized_status(struct rq *rq) { }
>
Yes. Thanks for catching. I made a mistake there.
>> +
>> +static inline void set_rd_overutilized_status(struct root_domain *rd,
>> + unsigned int status)
>> +{
>> + return 0;
>> +}
>
> static inline void set_rd_overutilized_status(struct rq *rq) { }
>
> my comment on v4 about {return 0; } applies only for static inline int
> is_rd_overutilized(struct root_domain *rd)
>
> Also, I don't think that set_rd_overutilized_status() is called
> outside #ifdef CONFIG_SMP so you can remove it.
>
yes. this set_rd_overutilized_status and is_rd_overutilized or is_rd_not_overutilized
can go away for !CONFIG_SMP case. Let me do that and send next version.
>
>
>
next prev parent reply other threads:[~2024-03-07 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 10:24 [PATCH v5 0/3] sched/fair: Limit access to overutilized Shrikanth Hegde
2024-03-06 10:24 ` [PATCH v5 1/3] sched/fair: Add EAS checks before updating overutilized Shrikanth Hegde
2024-03-06 17:40 ` Vincent Guittot
2024-03-07 4:50 ` Shrikanth Hegde [this message]
2024-03-06 10:24 ` [PATCH v5 2/3] sched/fair: Use helper function to access rd->overutilized Shrikanth Hegde
2024-03-06 17:40 ` Vincent Guittot
2024-03-06 10:24 ` [PATCH v5 3/3] sched/fair: Combine EAS check with overutilized access Shrikanth Hegde
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=61ef7ebd-f5cf-4d48-9bbd-f011d751041a@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=aboorvad@linux.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nysal@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=srikar@linux.ibm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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®