From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us,
vinicius.gomes@intel.com, kurt@linutronix.de,
gerhard@engleder-embedded.com, amritha.nambiar@intel.com,
ferenc.fejes@ericsson.com, xiaoliang.yang_1@nxp.com,
rogerq@kernel.org, pranavi.somisetty@amd.com,
harini.katakam@amd.com, peppe.cavallaro@st.com,
alexandre.torgue@foss.st.com, michael.wei.hong.sit@intel.com,
mohammad.athari.ismail@intel.com, linux@rempel-privat.de,
jacob.e.keller@intel.com, linux-kernel@vger.kernel.org,
andrew@lunn.ch, f.fainelli@gmail.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
horatiu.vultur@microchip.com, joabreu@synopsys.com,
mcoquelin.stm32@gmail.com, intel-wired-lan@lists.osuosl.org,
muhammad.husaini.zulkifli@intel.com
Subject: Re: [PATCH net-next 0/5] xstats for tc-taprio
Date: Wed, 31 May 2023 09:10:26 +0000 [thread overview]
Message-ID: <168552422626.12579.6601125654059435231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230530091948.1408477-1-vladimir.oltean@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 30 May 2023 12:19:43 +0300 you wrote:
> As a result of this discussion:
> https://lore.kernel.org/intel-wired-lan/20230411055543.24177-1-muhammad.husaini.zulkifli@intel.com/
>
> it became apparent that tc-taprio should make an effort to standardize
> statistics counters related to the 802.1Qbv scheduling as implemented
> by the NIC. I'm presenting here one counter suggested by the standard,
> and one counter defined by the NXP ENETC controller from LS1028A. Both
> counters are reported globally and per traffic class - drivers get
> different callbacks for reporting both of these, and get to choose what
> to report in both cases.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net/sched: taprio: don't overwrite "sch" variable in taprio_dump_class_stats()
https://git.kernel.org/netdev/net-next/c/dced11ef84fb
- [net-next,2/5] net/sched: taprio: replace tc_taprio_qopt_offload :: enable with a "cmd" enum
https://git.kernel.org/netdev/net-next/c/2d800bc500fb
- [net-next,3/5] net/sched: taprio: add netlink reporting for offload statistics counters
https://git.kernel.org/netdev/net-next/c/6c1adb650c8d
- [net-next,4/5] net: enetc: refactor enetc_setup_tc_taprio() to have a switch/case for cmd
https://git.kernel.org/netdev/net-next/c/5353599aa745
- [net-next,5/5] net: enetc: report statistics counters for taprio
https://git.kernel.org/netdev/net-next/c/4802fca8d1af
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-31 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 9:19 [PATCH net-next 0/5] xstats for tc-taprio Vladimir Oltean
2023-05-30 9:19 ` [PATCH net-next 1/5] net/sched: taprio: don't overwrite "sch" variable in taprio_dump_class_stats() Vladimir Oltean
2023-05-30 21:14 ` Vinicius Costa Gomes
2023-05-30 21:32 ` Vladimir Oltean
2023-05-30 22:33 ` Vinicius Costa Gomes
2023-05-30 9:19 ` [PATCH net-next 2/5] net/sched: taprio: replace tc_taprio_qopt_offload :: enable with a "cmd" enum Vladimir Oltean
2023-05-30 12:01 ` Horatiu Vultur
2023-05-30 12:20 ` Kurt Kanzenbach
2023-05-30 12:45 ` Zulkifli, Muhammad Husaini
2023-05-30 20:50 ` Gerhard Engleder
2023-05-31 17:08 ` Simon Horman
2023-05-31 17:10 ` Vladimir Oltean
2023-05-30 9:19 ` [PATCH net-next 3/5] net/sched: taprio: add netlink reporting for offload statistics counters Vladimir Oltean
2023-05-30 22:52 ` Vinicius Costa Gomes
2023-05-31 13:33 ` Vladimir Oltean
2023-05-31 10:54 ` Zulkifli, Muhammad Husaini
2023-05-30 9:19 ` [PATCH net-next 4/5] net: enetc: refactor enetc_setup_tc_taprio() to have a switch/case for cmd Vladimir Oltean
2023-05-30 9:19 ` [PATCH net-next 5/5] net: enetc: report statistics counters for taprio Vladimir Oltean
2023-05-31 9:10 ` patchwork-bot+netdevbpf [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=168552422626.12579.6601125654059435231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amritha.nambiar@intel.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=ferenc.fejes@ericsson.com \
--cc=gerhard@engleder-embedded.com \
--cc=harini.katakam@amd.com \
--cc=horatiu.vultur@microchip.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=mohammad.athari.ismail@intel.com \
--cc=muhammad.husaini.zulkifli@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=pranavi.somisetty@amd.com \
--cc=rogerq@kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=xiyou.wangcong@gmail.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;
as well as URLs for NNTP newsgroup(s).