From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Ferenc Fejes <ferenc.fejes@ericsson.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Gerhard Engleder <gerhard@engleder-embedded.com>,
"Y.B. Lu" <yangbo.lu@nxp.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Richard Cochran <richardcochran@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Kurt Kanzenbach <kurt@linutronix.de>,
Yannick Vignon <yannick.vignon@nxp.com>,
Rui Sousa <rui.sousa@nxp.com>, Jiri Pirko <jiri@nvidia.com>,
Ido Schimmel <idosch@nvidia.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>
Subject: Re: [PATCH v2 net-next] selftests: forwarding: add Per-Stream Filtering and Policing test for Ocelot
Date: Thu, 26 May 2022 00:50:22 +0000 [thread overview]
Message-ID: <20220526005021.l5motcuqdotkqngm@skbuf> (raw)
In-Reply-To: <c2730450-1f2b-8cb9-d56c-6bb8a35f0267@ericsson.com>
On Fri, May 06, 2022 at 12:24:37PM +0000, Ferenc Fejes wrote:
> Hi Vladimir!
>
> On 2022. 05. 06. 14:01, Vladimir Oltean wrote:
> > Hi Ferenc,
> >
> > On Fri, May 06, 2022 at 07:49:40AM +0000, Ferenc Fejes wrote:
> > This is correct. I have been testing only with the offloaded tc-gate
> > action so I did not notice that the software does not act upon the ipv.
> > Your proposal sounds straightforward enough. Care to send a bug fix patch?
>
> Unfortunately I cant, our company policy does not allow direct
> open-source contributions :-(
>
> However I would be more than happy if you can fix it.
That's too bad.
I have a patch which I am still testing, but you've managed to captivate
my attention for saying that you are testing 802.1Qch with a software
implementation of tc-gate.
Do you have a use case for this? What cycle times are you targeting?
How are you ensuring that you are deterministically meeting the deadlines?
Do you also have a software tc-taprio on the egress device or is that
at least offloaded?
I'm asking these questions because the peristaltic shaper is primarily
intended to be used on hardware switches. The patch I'm preparing
includes changes to struct sk_buff. I just want to know how well I'll be
able to sell these changes to maintainers strongly opposing the growth
of this structure for an exceedingly small niche :)
next prev parent reply other threads:[~2022-05-26 0:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 11:29 [PATCH v2 net-next] selftests: forwarding: add Per-Stream Filtering and Policing test for Ocelot Vladimir Oltean
2022-05-01 11:56 ` Kurt Kanzenbach
2022-05-02 23:10 ` patchwork-bot+netdevbpf
2022-05-06 7:49 ` Ferenc Fejes
2022-05-06 12:01 ` Vladimir Oltean
2022-05-06 12:24 ` Ferenc Fejes
2022-05-26 0:50 ` Vladimir Oltean [this message]
2022-05-26 6:40 ` Ferenc Fejes
2022-05-26 9:30 ` Vladimir Oltean
2023-02-16 13:47 ` Ferenc Fejes
2023-02-16 15:58 ` Vladimir Oltean
2023-02-17 8:03 ` Ferenc Fejes
2023-02-17 13:07 ` Vladimir Oltean
2023-02-17 14:35 ` Ferenc Fejes
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=20220526005021.l5motcuqdotkqngm@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--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=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rui.sousa@nxp.com \
--cc=shuah@kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vivien.didelot@gmail.com \
--cc=xiaoliang.yang_1@nxp.com \
--cc=yangbo.lu@nxp.com \
--cc=yannick.vignon@nxp.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