Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
	Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: andy@kernel.org, michal.swiatkowski@linux.intel.com,
	wojciech.drewek@intel.com, idosch@nvidia.com,
	jesse.brandeburg@intel.com, kuba@kernel.org,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	simon.horman@corigine.com, jiri@resnulli.us, pabeni@redhat.com,
	davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support
Date: Mon, 11 Dec 2023 13:38:48 +0100	[thread overview]
Message-ID: <13f7d3b4-214c-4987-9adc-1c14ae686946@intel.com> (raw)
In-Reply-To: <b3e5ec09-d01b-0cea-69ea-c7406ea3f8b5@intel.com>

From: Tony Nguyen <anthony.l.nguyen@intel.com>
Date: Fri, 8 Dec 2023 13:34:10 -0800

> 
> 
> On 12/7/2023 8:49 AM, Marcin Szycik wrote:
>> Add support for creating PFCP filters in switchdev mode. Add pfcp module
>> that allows to create a PFCP-type netdev. The netdev then can be
>> passed to
>> tc when creating a filter to indicate that PFCP filter should be created.
>>
>> To add a PFCP filter, a special netdev must be created and passed to tc
>> command:
>>
>>    ip link add pfcp0 type pfcp
>>    tc filter add dev eth0 ingress prio 1 flower pfcp_opts \
>>      1:12ab/ff:fffffffffffffff0 skip_hw action mirred egress redirect \
>>      dev pfcp0
>>
>> Changes in iproute2 [1] are required to use pfcp_opts in tc.
>>
>> ICE COMMS package is required as it contains PFCP profiles.
>>
>> Part of this patchset modifies IP_TUNNEL_*_OPTs, which were previously
>> stored in a __be16. All possible values have already been used, making it
>> impossible to add new ones.
>>
>> [1]
>> https://lore.kernel.org/netdev/20230614091758.11180-1-marcin.szycik@linux.intel.com
>> ---
>> This patchset should be applied on top of the "boys" tree [2], as it
>> depends on recent bitmap changes.
> 
> Is this for comment only (RFC)? This doesn't seem to apply to iwl-next
> and if this based on, and has dependencies from, another tree, I can't
> apply them here.

It's not an RFC.
The series contains generic code changes and must go directly through
net-next. The dependency on the bitmap tree was discussed with Jakub and
Yury and we agreed that the netdev guys will pull it before applying
this one.

Thanks,
Olek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2023-12-11 12:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 16:49 [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 1/7] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 2/7] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 3/7] lib/bitmap: add tests for IP tunnel flags conversion helpers Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 4/7] pfcp: add PFCP module Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 5/7] pfcp: always set pfcp metadata Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 6/7] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 7/7] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-12-08 21:34 ` [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support Tony Nguyen
2023-12-11 12:38   ` Alexander Lobakin [this message]
2023-12-11 21:23     ` Tony Nguyen
2023-12-12 10:45       ` Marcin Szycik
2023-12-15 10:11         ` Alexander Lobakin
2023-12-15 16:49           ` Jakub Kicinski
2023-12-18 10:04             ` Marcin Szycik
2023-12-18 12:47               ` Alexander Lobakin
2023-12-18 15:57                 ` Yury Norov
2023-12-18 16:16                   ` Alexander Potapenko
2023-12-19  9:04                     ` Alexander Lobakin

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=13f7d3b4-214c-4987-9adc-1c14ae686946@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=andy@kernel.org \
    --cc=anthony.l.nguyen@intel.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=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@corigine.com \
    --cc=wojciech.drewek@intel.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