From: Vladimir Oltean <olteanv@gmail.com>
To: "Somisetty, Pranavi" <pranavi.somisetty@amd.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"git (AMD-Xilinx)" <git@amd.com>,
"Katakam, Harini" <harini.katakam@amd.com>,
"Pandey, Radhey Shyam" <radhey.shyam.pandey@amd.com>,
"Simek, Michal" <michal.simek@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 0/2] Add support for Frame preemption (IEEE
Date: Fri, 4 Nov 2022 17:52:24 +0200 [thread overview]
Message-ID: <20221104155224.jqj5axtp5jt77yqt@skbuf> (raw)
In-Reply-To: <BN8PR12MB28528DB6C999C7608958B284F73B9@BN8PR12MB2852.namprd12.prod.outlook.com>
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@nxp.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.
prev parent reply other threads:[~2022-11-04 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 11:33 [RFC PATCH net-next 0/2] Add support for Frame preemption (IEEE Pranavi Somisetty
2022-11-03 11:33 ` [RFC PATCH net-next 1/2] include: uapi: Add new ioctl definitions to support Frame Preemption Pranavi Somisetty
2022-11-03 22:11 ` Andrew Lunn
2022-11-03 11:33 ` [RFC PATCH net-next 2/2] include: uapi: Add Frame preemption parameters Pranavi Somisetty
2022-11-03 22:51 ` [RFC PATCH net-next 0/2] Add support for Frame preemption (IEEE Vladimir Oltean
2022-11-04 14:08 ` Somisetty, Pranavi
2022-11-04 15:52 ` Vladimir Oltean [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=20221104155224.jqj5axtp5jt77yqt@skbuf \
--to=olteanv@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pranavi.somisetty@amd.com \
--cc=radhey.shyam.pandey@amd.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