On Tue, 19 May 2020 07:38:57 +0000 Ioana Ciornei wrote: > > Subject: Re: [PATCH v2 net-next 0/7] dpaa2-eth: add support for Rx traffic > > classes > > > > On Sat, 16 May 2020 08:16:47 +0000 Ioana Ciornei wrote: > > > > With the Rx QoS features users won't even be able to tell via > > > > standard Linux interfaces what the config was. > > > > > > Ok, that is true. So how should this information be exported to the user? > > > > > > > I believe no such interface currently exists. > > I am having a bit of trouble understanding what should be the route > for this feature to get accepted.
What's the feature you're trying to get accepted? Driver's datapath to behave correctly when some proprietary out-of-tree API is used to do the actual configuration? Unexciting. > Is the problem having the classification to a TC based on the VLAN > PCP or is there anything else? What you have is basically RX version of mqprio, right? Multiple rings per "channel" each gets frames with specific priorities? This needs to be well integrated with the rest of the stack, but I don't think TC qdisc offload is a fit. Given we don't have qdiscs on ingress. As I said a new API for this would most likely have to be created.
