From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: krzk@kernel.org, andersson@kernel.org, konradybcio@kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: Tips on tracing bwmon?
Date: Thu, 22 Oct 2026 11:44:20 +0000 [thread overview]
Message-ID: <atn3FAF-3GHPgvad@gallifrey> (raw)
In-Reply-To: <87e38bda-7ec2-4b7f-84c9-29a837696572@oss.qualcomm.com>
* Konrad Dybcio (konrad.dybcio@oss.qualcomm.com) wrote:
> On 10/20/26 4:27 PM, Dr. David Alan Gilbert wrote:
> > Hi all,
> > I was looking for some tips on if I can use bwmon to see what interconnect
> > bandwidth is going through the dwc3 usb controllers on my x1 based Asus Zenbook A14.
> >
> > I've got usb-ncm gadget wired between a pair of them and I'd
> > like to see what stats are available;
> > (See details of my gadget stuff setup in
> > https://lore.kernel.org/linux-arm-msm/atJn2jfI_cZy3UMo@gallifrey/T/#u )
> > And that's struggling to get much over 4Gbit/s over the network interface.
> >
> > One reason I'm curious is because the dwc3-qcom glue sets an average
> > and a peak icc limit, and I wanted to know what the difference was and
> > what the type of timescales were for how long it allowed a peak.
> >
> > Are there any docs I should look at?
> >
> > I did:
> > trace-cmd stream -e icc_bwmon:qcom_bwmon_update > log
> > on both machines and during the run I'm seeing events on exactly 3 of the
> > monitors;
> > 24091000.pmu, 240b5400.pmu, 240b6400.pmu
> >
> > (In the numbers below I've grepped for that monitor and sed'ed out
> > upto the 'measu_kbps=' part so I can then sort on the meas_kbps)
> >
> > My reading of the interconnects_summary is these PMUs are
> > somewhere under the llcc_mc@interconnect-1, and in some
> > cases under both chm_apps@ and qns_llcc
>
> These BWMONs only monitor the CPU-DRAM paths
Thanks for the reply and explanation.
Are there other BWMONs that should show the USB path bandwidth,
and if so how would I watch them?
Thanks again,
> Konrad
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2026-10-22 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 14:27 Tips on tracing bwmon? Dr. David Alan Gilbert
2026-10-22 9:12 ` Konrad Dybcio
2026-10-22 11:44 ` Dr. David Alan Gilbert [this message]
2026-10-26 13:52 ` Konrad Dybcio
2026-10-26 14:21 ` Dr. David Alan Gilbert
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=atn3FAF-3GHPgvad@gallifrey \
--to=dave@treblig.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.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