[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221104155224.jqj5axtp5jt77yqt@skbuf>
Date: Fri, 4 Nov 2022 17:52:24 +0200
From: Vladimir Oltean <olteanv@...il.com>
To: "Somisetty, Pranavi" <pranavi.somisetty@....com>
Cc: "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"git (AMD-Xilinx)" <git@....com>,
"Katakam, Harini" <harini.katakam@....com>,
"Pandey, Radhey Shyam" <radhey.shyam.pandey@....com>,
"Simek, Michal" <michal.simek@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [RFC PATCH net-next 0/2] Add support for Frame preemption (IEEE
On Fri, Nov 04, 2022 at 02:08:25PM +0000, Somisetty, Pranavi wrote:
> > Have you seen:
> > https://patchwork.kernel.org/project/netdevbpf/cover/20220816222920.195
> > 2936-1-vladimir.oltean@....com/
>
> Thanks Vladimir, I hadn't, we will try to use your RFC.
The point is not to *use* it (you can't even without some major effort -
I didn't even publish the user space patches, even though I have ethtool
ready and openlldp almost completely ready as well; plus I also did some
more rework to the posted RFC, which I didn't repost yet).
The point is that the RFC has stalled due to seemingly no clear answers
to some fundamental questions about the placement of these new features.
It would be good if some extra feedback from people familiar with frame
preemption/MAC merge could be provided there.
Thanks.
Powered by blists - more mailing lists