From: Jakub Kicinski <kuba@kernel.org>
To: "Zulkifli, Muhammad Husaini" <muhammad.husaini.zulkifli@intel.com>
Cc: "tee.min.tan@linux.intel.com" <tee.min.tan@linux.intel.com>,
"intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v2] igc: Add TransmissionOverrun counter
Date: Tue, 2 May 2023 08:27:34 -0700 [thread overview]
Message-ID: <20230502082734.0f2f88b1@kernel.org> (raw)
In-Reply-To: <SJ1PR11MB6180117EC9550B1993944DE7B86F9@SJ1PR11MB6180.namprd11.prod.outlook.com>
On Tue, 2 May 2023 01:47:30 +0000 Zulkifli, Muhammad Husaini wrote:
> > Seems like something that should be reported back to the qdisc which
> > configured the gate.
>
> May I know which qdisc stats that we need to reported out? Is it gnet_stats_queue?
> IMHO, gnet_stats_queue stats all used by SW QBV and not by HW QBV.
Yeah, definitely not gnet_stats_queue, the qdisc used to configure
the gates can have its dedicated super special stats.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-05-02 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 5:55 [Intel-wired-lan] [PATCH net-next v2] igc: Add TransmissionOverrun counter Muhammad Husaini Zulkifli
2023-04-18 23:51 ` Tony Nguyen
2023-04-19 0:19 ` Jakub Kicinski
2023-05-02 1:47 ` Zulkifli, Muhammad Husaini
2023-05-02 15:27 ` Jakub Kicinski [this message]
2023-05-28 10:10 ` Zulkifli, Muhammad Husaini
2023-05-29 13:59 ` Vladimir Oltean
2023-05-29 17:33 ` Vladimir Oltean
2023-05-30 2:08 ` Jakub Kicinski
2023-05-30 2:56 ` Zulkifli, Muhammad Husaini
2023-05-30 8:31 ` Vladimir Oltean
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=20230502082734.0f2f88b1@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=tee.min.tan@linux.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