From: Simon Horman <simon.horman@corigine.com>
To: Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: jiri@resnulli.us, netdev@vger.kernel.org, idosch@nvidia.com,
jesse.brandeburg@intel.com, kuba@kernel.org,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [RFC PATCH iwl-next 3/6] pfcp: add PFCP module
Date: Mon, 5 Jun 2023 11:26:09 +0200 [thread overview]
Message-ID: <ZH2qMZ4gbdSiDE66@corigine.com> (raw)
In-Reply-To: <20230601131929.294667-4-marcin.szycik@linux.intel.com>
On Thu, Jun 01, 2023 at 03:19:26PM +0200, Marcin Szycik wrote:
> From: Wojciech Drewek <wojciech.drewek@intel.com>
>
> Packet Forwarding Control Protocol (PFCP) is a 3GPP Protocol
> used between the control plane and the user plane function.
> It is specified in TS 29.244[1].
>
> Note that this module is not designed to support this Protocol
> in the kernel space. There is no support for parsing any PFCP messages.
> There is no API that could be used by any userspace daemon.
> Basically it does not support PFCP. This protocol is sophisticated
> and there is no need for implementing it in the kernel. The purpose
> of this module is to allow users to setup software and hardware offload
> of PFCP packets using tc tool.
>
> When user requests to create a PFCP device, a new socket is created.
> The socket is set up with port number 8805 which is specific for
> PFCP [29.244 4.2.2]. This allow to recive PFCP request messages,
> response messages use other ports.
nit: s/recive/receive/
>
> Note that only one PFCP netdev can be created.
>
> Only IPv4 is supported at this time.
>
> [1] https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3111
>
> Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <simon.horman@corigine.com>
To: Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
wojciech.drewek@intel.com, michal.swiatkowski@linux.intel.com,
alexandr.lobakin@intel.com, davem@davemloft.net, kuba@kernel.org,
jiri@resnulli.us, pabeni@redhat.com, jesse.brandeburg@intel.com,
idosch@nvidia.com
Subject: Re: [RFC PATCH iwl-next 3/6] pfcp: add PFCP module
Date: Mon, 5 Jun 2023 11:26:09 +0200 [thread overview]
Message-ID: <ZH2qMZ4gbdSiDE66@corigine.com> (raw)
In-Reply-To: <20230601131929.294667-4-marcin.szycik@linux.intel.com>
On Thu, Jun 01, 2023 at 03:19:26PM +0200, Marcin Szycik wrote:
> From: Wojciech Drewek <wojciech.drewek@intel.com>
>
> Packet Forwarding Control Protocol (PFCP) is a 3GPP Protocol
> used between the control plane and the user plane function.
> It is specified in TS 29.244[1].
>
> Note that this module is not designed to support this Protocol
> in the kernel space. There is no support for parsing any PFCP messages.
> There is no API that could be used by any userspace daemon.
> Basically it does not support PFCP. This protocol is sophisticated
> and there is no need for implementing it in the kernel. The purpose
> of this module is to allow users to setup software and hardware offload
> of PFCP packets using tc tool.
>
> When user requests to create a PFCP device, a new socket is created.
> The socket is set up with port number 8805 which is specific for
> PFCP [29.244 4.2.2]. This allow to recive PFCP request messages,
> response messages use other ports.
nit: s/recive/receive/
>
> Note that only one PFCP netdev can be created.
>
> Only IPv4 is supported at this time.
>
> [1] https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3111
>
> Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
next prev parent reply other threads:[~2023-06-05 9:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 13:19 [Intel-wired-lan] [RFC PATCH iwl-next 0/6] ice: Add PFCP filter support Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 1/6] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-05 9:23 ` [Intel-wired-lan] " Simon Horman
2023-06-05 9:23 ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 2/6] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-02 13:19 ` [Intel-wired-lan] " Alexander Lobakin
2023-06-02 13:19 ` Alexander Lobakin
2023-06-03 7:40 ` kernel test robot
2023-06-05 9:23 ` [Intel-wired-lan] " Simon Horman
2023-06-05 9:23 ` Simon Horman
2023-06-05 14:21 ` [Intel-wired-lan] " Marcin Szycik
2023-06-05 14:21 ` Marcin Szycik
2023-06-06 13:17 ` [Intel-wired-lan] " Alexander Lobakin
2023-06-06 13:17 ` Alexander Lobakin
2023-06-06 15:25 ` [Intel-wired-lan] " Simon Horman
2023-06-06 15:25 ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 3/6] pfcp: add PFCP module Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-05 9:26 ` Simon Horman [this message]
2023-06-05 9:26 ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 4/6] pfcp: always set pfcp metadata Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-05 9:34 ` [Intel-wired-lan] " Simon Horman
2023-06-05 9:34 ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 5/6] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-05 9:36 ` [Intel-wired-lan] " Simon Horman
2023-06-05 9:36 ` Simon Horman
2023-06-01 13:19 ` [Intel-wired-lan] [RFC PATCH iwl-next 6/6] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-06-01 13:19 ` Marcin Szycik
2023-06-05 9:38 ` [Intel-wired-lan] " Simon Horman
2023-06-05 9:38 ` Simon Horman
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=ZH2qMZ4gbdSiDE66@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.