From: Pranavi Somisetty <pranavi.somisetty@amd.com>
To: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>
Cc: <git@amd.com>, <pranavi.somisetty@amd.com>,
<harini.katakam@amd.com>, <radhey.shyam.pandey@amd.com>,
<michal.simek@amd.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: [RFC PATCH net-next 0/2] Add support for Frame preemption (IEEE
Date: Thu, 3 Nov 2022 05:33:46 -0600 [thread overview]
Message-ID: <20221103113348.17378-1-pranavi.somisetty@amd.com> (raw)
Frame Preemption is one of the core standards of TSN. It enables
low latency trasmission of time-critical frames by allowing them to
interrupt the transmission of other non time-critical traffic. Frame
preemption is only active when the link partner is also capable of it.
This negotiation is done using LLDP as specified by the standard. Open
source lldp utilities and other applications, can make use of
the ioctls and the header being here, to query preemption capabilities
and configure various parameters.
Pranavi Somisetty (2):
include: uapi: Add new ioctl definitions to support Frame Preemption
include: uapi: Add Frame preemption parameters
include/uapi/linux/preemption_8023br.h | 30 ++++++++++++++++++++++++++
include/uapi/linux/sockios.h | 6 ++++++
net/core/dev_ioctl.c | 6 +++++-
3 files changed, 41 insertions(+), 1 deletion(-)
create mode 100644 include/uapi/linux/preemption_8023br.h
--
2.36.1
next reply other threads:[~2022-11-03 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 11:33 Pranavi Somisetty [this message]
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
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=20221103113348.17378-1-pranavi.somisetty@amd.com \
--to=pranavi.somisetty@amd.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=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
all inboxes | Powered by JetHome®