From: Wojciech Drewek <wojciech.drewek@intel.com>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org
Subject: [PATCH iproute2-next 1/2] ip: PFCP device support
Date: Wed, 10 Apr 2024 12:14:39 +0200 [thread overview]
Message-ID: <20240410101440.9885-2-wojciech.drewek@intel.com> (raw)
In-Reply-To: <20240410101440.9885-1-wojciech.drewek@intel.com>
Packet Forwarding Control Protocol is a 3GPP Protocol defined in
TS 29.244 [1]. Add support for PFCP device type in ip link.
It is capable of receiving PFCP messages and extracting its
metadata (session ID).
Its only purpose is to be used together with tc flower to create
SW/HW filters.
PFCP module does not take any netlink attributes so there is no
need to parse any args. Add new sections to the man to let the
user know about new device type.
[1] https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3111
Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
---
ip/iplink.c | 2 +-
man/man8/ip-link.8.in | 10 ++++++++++
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/ip/iplink.c b/ip/iplink.c
index 95314af5ab1c..73d4cd428047 100644
--- a/ip/iplink.c
+++ b/ip/iplink.c
@@ -44,7 +44,7 @@ void iplink_types_usage(void)
" ip6erspan | ip6gre | ip6gretap | ip6tnl |\n"
" ipip | ipoib | ipvlan | ipvtap |\n"
" macsec | macvlan | macvtap | netdevsim |\n"
- " netkit | nlmon | rmnet | sit | team | team_slave |\n"
+ " netkit | nlmon | pfcp | rmnet | sit | team | team_slave |\n"
" vcan | veth | vlan | vrf | vti | vxcan | vxlan | wwan |\n"
" xfrm | virt_wifi }\n");
}
diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
index 31e2d7f0f5b8..2654f8c361ae 100644
--- a/man/man8/ip-link.8.in
+++ b/man/man8/ip-link.8.in
@@ -249,6 +249,7 @@ ip-link \- network device configuration
.BR netdevsim " |"
.BR netkit " |"
.BR nlmon " |"
+.BR pfcp " |"
.BR rmnet " |"
.BR sit " |"
.BR vcan " | "
@@ -391,6 +392,9 @@ Link types:
.BR nlmon
- Netlink monitoring device
.sp
+.BR pfcp
+- Packet Forwarding Control Protocol device
+.sp
.BR rmnet
- Qualcomm rmnet device
.sp
@@ -2124,6 +2128,12 @@ the following additional arguments are supported:
.BI restart_count " RESTART_COUNT "
- GTP instance restart counter
+.TP
+PFCP Type Support
+For a link of type
+.I PFCP
+no additional arguments are supported
+
.in -8
.SS ip link delete - delete virtual link
--
2.40.1
next prev parent reply other threads:[~2024-04-10 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 10:14 [PATCH iproute2-next 0/2] PFCP support Wojciech Drewek
2024-04-10 10:14 ` Wojciech Drewek [this message]
2024-04-10 10:14 ` [PATCH iproute2-next 2/2] f_flower: implement pfcp opts Wojciech Drewek
2024-04-10 15:53 ` Stephen Hemminger
2024-04-11 11:32 ` Wojciech Drewek
2024-04-12 14:41 ` David Ahern
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=20240410101440.9885-2-wojciech.drewek@intel.com \
--to=wojciech.drewek@intel.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.