From: Changwoo Min <changwoo@igalia.com>
To: Andrea Righi <arighi@nvidia.com>, Tejun Heo <tj@kernel.org>
Cc: void@manifault.com, kernel-dev@igalia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] sched_ext: Add a core event and update scx schedulers
Date: Sat, 8 Feb 2025 12:17:26 +0900 [thread overview]
Message-ID: <aedaba97-08a4-47bd-bb0d-7192dc2a91a5@igalia.com> (raw)
In-Reply-To: <Z6Z_CNBMp5greLf4@gpd3>
Hi Tejun and Andrea,
On 25. 2. 8. 06:45, Andrea Righi wrote:
> On Fri, Feb 07, 2025 at 11:38:31AM -1000, Tejun Heo wrote:
>> I'm not sure. BPF schedulers should be able to avoid getting the default
>> slice. Hopefully, with the added visibility, this should be easier now. I'm
>> not sure how much overriding the default value in ops helps in terms of
>> control. It's a very half-way measure. Instead, how about we add tracepoint
>> to scx_add_event() so that folks who want to get backtrace of specific
>> events can get them easily so that it's easier to debug where these counts
>> are coming from? Let's just make it easier to avoid these events.
>
> Yeah, that's a valid point, the implicit SCX_SLICE_DFL should be seen as a
> countermeasure for unhandled situations. Instead of fixing the
> countermeasure itself we should try to prevent it, if it proves to be
> problematic. And I like the idea of having a way to backtrace specific
> events.
I agree that adding a tracepoint to scx_add_event() and
__scx_add_event() is a defenitely useful extension to further
investigate what's going on. I will take a look.
Regards,
Changwoo Min
prev parent reply other threads:[~2025-02-08 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 3:13 [PATCH 0/2] sched_ext: Add a core event and update scx schedulers Changwoo Min
2025-02-07 3:13 ` [PATCH 1/2] sched_ext: Add an event, SCX_EV_ENQ_SLICE_DFL Changwoo Min
2025-02-07 6:17 ` Andrea Righi
2025-02-07 6:28 ` Changwoo Min
2025-02-07 3:13 ` [PATCH 2/2] sched_ext: Print an event, SCX_EV_ENQ_SLICE_DFL, in scx_qmap/central Changwoo Min
2025-02-07 6:24 ` [PATCH 0/2] sched_ext: Add a core event and update scx schedulers Andrea Righi
2025-02-07 6:49 ` Changwoo Min
2025-02-07 6:53 ` Andrea Righi
2025-02-07 21:38 ` Tejun Heo
2025-02-07 21:45 ` Andrea Righi
2025-02-08 3:17 ` Changwoo Min [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=aedaba97-08a4-47bd-bb0d-7192dc2a91a5@igalia.com \
--to=changwoo@igalia.com \
--cc=arighi@nvidia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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