From: Tejun Heo <tj@kernel.org>
To: Changwoo Min <changwoo@igalia.com>
Cc: Andrea Righi <arighi@nvidia.com>,
void@manifault.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched_ext: Add trace point to track sched_ext core events
Date: Fri, 28 Feb 2025 13:50:36 -1000 [thread overview]
Message-ID: <Z8JLzOBMGvvAtu54@slm.duckdns.org> (raw)
In-Reply-To: <86a6c5c7-47b7-49af-af57-b1d2171ba97c@igalia.com>
Hello,
On Sat, Mar 01, 2025 at 08:33:36AM +0900, Changwoo Min wrote:
...
> You might have two options here: 1) returning per-CPU event
> counter or 2) returning aggregated event counter. The first opion
> will be fast but less meaningful from user's point of view
> compared to the second option. Assuming the tracepoint are not in
> the hot path, I think the second option will be better choice.
> I will add an @event field and a special version of
> scx_bpf_events() for faster aggregation.
Ah, right, let's forget about printing aggregate for now. That's not
difficult for anyone to find out if necessary after all.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-02-28 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 8:59 [PATCH v2] sched_ext: Add trace point to track sched_ext core events Changwoo Min
2025-02-28 10:03 ` Andrea Righi
2025-02-28 17:31 ` Tejun Heo
2025-02-28 23:33 ` Changwoo Min
2025-02-28 23:50 ` Tejun Heo [this message]
2025-03-01 0:46 ` Changwoo Min
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=Z8JLzOBMGvvAtu54@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.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