ice: PPPoE offload support
Subsystems (4)
v3 cover ice: PPPoE offload support
Add support for dissecting PPPoE and PPP-specific fields in flow dissector:
PPPoE session id and PPP protocol type. Add support for those fields in tc-flower and support offloading PPPoE. Finally, add support for hardware offload of PPPoE packets in switchdev mode in ice driver.
Example filter:
tc filter add dev $PF1 ingress protocol ppp_ses prio 1 flower pppoe_sid \
1234 ppp_proto ip skip_sw action mirred egress redirect dev $VF1_PR
Changes in iproute2 are required to use the new fields (will be submitted soon).
ICE COMMS DDP package is required to create a filter in ice.
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
[0] https://patchwork.ozlabs.org/project/intel-wired-lan/patch/[email protected]
v3: revert byte order changes in is_ppp_proto_supported from previous
version, add kernel-doc for is_ppp_proto_supported, add more CC
v2: cosmetic changes
Marcin Szycik (1):
ice: Add support for PPPoE hardware offload
Wojciech Drewek (3):
flow_dissector: Add PPPoE dissectors
net/sched: flower: Add PPPoE filter
flow_offload: Introduce flow_match_pppoe
drivers/net/ethernet/intel/ice/ice.h | 1 + .../net/ethernet/intel/ice/ice_flex_pipe.c | 5 +- .../ethernet/intel/ice/ice_protocol_type.h | 11 ++ drivers/net/ethernet/intel/ice/ice_switch.c | 165 ++++++++++++++++++ drivers/net/ethernet/intel/ice/ice_tc_lib.c | 95 ++++++++-- drivers/net/ethernet/intel/ice/ice_tc_lib.h | 8 + include/net/flow_dissector.h | 11 ++ include/net/flow_offload.h | 6 + include/uapi/linux/pkt_cls.h | 3 + net/core/flow_dissector.c | 55 +++++- net/core/flow_offload.c | 7 + net/sched/cls_flower.c | 46 +++++ 12 files changed, 396 insertions(+), 17 deletions(-)
Signature · 6 lines
2.35.1 _______________________________________________ Intel-wired-lan mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
RFC PATCH v3 1/4 flow_dissector: Add PPPoE dissectors
From: Wojciech Drewek <[email protected]>
Allow to dissect PPPoE specific fields which are:
- session ID (16 bits)
- ppp protocol (16 bits)
The goal is to make the following TC command possible:
# tc filter add dev ens6f0 ingress prio 1 protocol ppp_ses \
flower \
pppoe_sid 12 \
ppp_proto ip \
action dropNote that only PPPoE Session is supported.
---
v3: revert byte order changes in is_ppp_proto_supported from previous
version, add kernel-doc for is_ppp_proto_supported
v2: use ntohs instead of htons in is_ppp_proto_supported
include/net/flow_dissector.h | 11 ++++++++ net/core/flow_dissector.c | 55 ++++++++++++++++++++++++++++++++---- 2 files changed, 60 insertions(+), 6 deletions(-)
include/net/flow_dissector.h +11 -0
@@ -261,6 +261,16 @@ struct flow_dissector_key_num_of_vlans {u8 num_of_vlans; }; +/** +* struct flow_dissector_key_pppoe: +* @session_id: pppoe session id +* @ppp_proto: ppp protocol +*/ +struct flow_dissector_key_pppoe { +u16 session_id; +__be16 ppp_proto; +}; +enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CONTROL ,/* struct flow_dissector_key_control */ FLOW_DISSECTOR_KEY_BASIC ,/* struct flow_dissector_key_basic */
@@ -291,6 +301,7 @@ enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CT ,/* struct flow_dissector_key_ct */ FLOW_DISSECTOR_KEY_HASH ,/* struct flow_dissector_key_hash */ FLOW_DISSECTOR_KEY_NUM_OF_VLANS ,/* struct flow_dissector_key_num_of_vlans */ +FLOW_DISSECTOR_KEY_PPPOE ,/* struct flow_dissector_key_pppoe */ FLOW_DISSECTOR_KEY_MAX, };
net/core/flow_dissector.c +49 -6
74 lines not on this page · raw message
Signature · 1 line
2.35.1
Re: [RFC PATCH net-next v3 1/4] flow_dissector: Add PPPoE dissectors
Quoted 33 lines · Marcin Szycik
From: Wojciech Drewek <[email protected]>
Allow to dissect PPPoE specific fields which are:
- session ID (16 bits)
- ppp protocol (16 bits)The goal is to make the following TC command possible:
# tc filter add dev ens6f0 ingress prio 1 protocol ppp_ses \ flower \ pppoe_sid 12 \ ppp_proto ip \ action dropNote that only PPPoE Session is supported.
Signed-off-by Wojciech Drewek <[email protected]>---
v3: revert byte order changes inis_ppp_proto_supportedfrom previous
version, add kernel-doc foris_ppp_proto_supported
v2: use ntohs instead of htons inis_ppp_proto_supportedinclude/net/flow_dissector.h | 11 ++++++++ net/core/flow_dissector.c | 55 ++++++++++++++++++++++++++++++++---- 2 files changed, 60 insertions(+), 6 deletions(-)include/net/flow_dissector.h +0
-0@@ -261,6 +261,16 @@ struct flow_dissector_key_num_of_vlans {u8 num_of_vlans; };
include/net/flow_dissector.h struct flow_dissector_key_num_of_vlans { · line 272
Quoted 10 lines
include/net/flow_dissector.h +9
-0+/** +* struct flow_dissector_key_pppoe: +* @session_id: pppoe session id +* @ppp_proto: ppp protocol +*/ +struct flow_dissector_key_pppoe { +u16 session_id; +__be16 ppp_proto; +};
Why isn't session_id __be16 too?
Also, I'm not sure I like mixing the PPPoE session ID and PPP protocol fields in the same structure: they're part of two different protocols. However, I can't anticipate any technical problem in doing so, and I guess there's no easy way to let the flow dissector parse the PPP header independently. So well, maybe we don't have choice...
Quoted 60 lines
include/net/flow_dissector.h +1
-0enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CONTROL ,/* struct flow_dissector_key_control */ FLOW_DISSECTOR_KEY_BASIC ,/* struct flow_dissector_key_basic */ @@ -291,6 +301,7 @@ enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CT ,/* struct flow_dissector_key_ct */ FLOW_DISSECTOR_KEY_HASH ,/* struct flow_dissector_key_hash */ FLOW_DISSECTOR_KEY_NUM_OF_VLANS ,/* struct flow_dissector_key_num_of_vlans */ +FLOW_DISSECTOR_KEY_PPPOE ,/* struct flow_dissector_key_pppoe */ FLOW_DISSECTOR_KEY_MAX, };net/core/flow_dissector.c +33
-1@@ -895,6 +895,39 @@ bool bpf_flow_dissect(struct bpf_prog *prog, struct bpf_flow_dissector *ctx,return result ==BPF_OK ; } +/** +* is_ppp_proto_supported - checks if inner PPP protocol should be dissected +* @proto: protocol type (PPP proto field) +*/ +static bool is_ppp_proto_supported (__be16 proto) +{ +switch (proto) { +case htons (PPP_AT ): +case htons (PPP_IPX ): +case htons (PPP_VJC_COMP ): +case htons (PPP_VJC_UNCOMP ): +case htons (PPP_MP ): +case htons (PPP_COMPFRAG ): +case htons (PPP_COMP ): +case htons (PPP_MPLS_UC ): +case htons (PPP_MPLS_MC ): +case htons (PPP_IPCP ): +case htons (PPP_ATCP ): +case htons (PPP_IPXCP ): +case htons (PPP_IPV6CP ): +case htons (PPP_CCPFRAG ): +case htons (PPP_MPLSCP ): +case htons (PPP_LCP ): +case htons (PPP_PAP ): +case htons (PPP_LQR ): +case htons (PPP_CHAP ): +case htons (PPP_CBCP ): +return true; +default : +return false; + } +} +/** * __skb_flow_dissect - extract the flow_keys struct and return it * @net: associated network namespace, derived from @skb if NULL @@ -1221,19 +1254,29 @@ bool __skb_flow_dissect(const struct net *net, } nhoff +=PPPOE_SES_HLEN ; -switch (hdr->proto) {
net/core/flow_dissector.c bool __skb_flow_dissect(const struct net *net, · line 1232
Quoted 10 lines
net/core/flow_dissector.c +2
-4-case htons (PPP_IP ): +if (hdr->proto ==htons (PPP_IP )) { proto =htons (ETH_P_IP ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ; -case htons (PPP_IPV6 ): + }else if (hdr->proto ==htons (PPP_IPV6 )) { proto =htons (ETH_P_IPV6 ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ;
1)
Looks like you could easily handle MPLS too. Did you skip it on purpose? (not enough users to justify writing and maintaining the code?).
I don't mean MPLS has to be supported; I'd just like to know if it was considered.
2)
Also this whole test is a bit weak: the version, type and code fields must have precise values for the PPPoE Session packet to be valid. If either version or type is different than 1, then the packet advertises a new version of the protocol that we don't know how to parse (or most probably the packet was forged or corrupted). A non-zero code is also invalid.
I know the code was already like this before your patch, but it's probably better to fix it before implementing hardware offload.
3)
Finally, the PPP protocol could be compressed and stored in 1 byte instead of 2. This case wasn't handled before your patch, but I think that should be fixed too before implementing hardware offload.
Quoted 24 lines
net/core/flow_dissector.c +14
-1-default : + }else if (is_ppp_proto_supported (hdr->proto)) { + fdret =FLOW_DISSECT_RET_OUT_GOOD ; + }else { fdret =FLOW_DISSECT_RET_OUT_BAD ;break ; } + +if (dissector_uses_key (flow_dissector, +FLOW_DISSECTOR_KEY_PPPOE )) { +struct flow_dissector_key_pppoe *key_pppoe; + + key_pppoe =skb_flow_dissector_target (flow_dissector, +FLOW_DISSECTOR_KEY_PPPOE , + target_container); + key_pppoe->session_id =ntohs (hdr->hdr.sid); + key_pppoe->ppp_proto = hdr->proto; + }break ; }case htons (ETH_P_TIPC ): {Signature · 1 line
2.35.1
RE: [RFC PATCH net-next v3 1/4] flow_dissector: Add PPPoE dissectors
Hi Guillaume,
Thanks for the review!
Quoted 48 lines
-----Original Message-----
From: Guillaume Nault <[email protected]>
Sent: piątek, 1 lipca 2022 01:10
To: Marcin Szycik <[email protected]>
Cc: [email protected]; Nguyen, Anthony L <[email protected]>; [email protected]; [email protected]; Brandeburg, Jesse <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Drewek, Wojciech <[email protected]>; Lobakin, Alexandr <[email protected]>; [email protected]; [email protected]
Subject: Re: [RFC PATCH net-next v3 1/4]flow_dissector: Add PPPoE dissectorsQuoted 34 lines · Marcin Szycik
From: Wojciech Drewek <[email protected]>
Allow to dissect PPPoE specific fields which are:
- session ID (16 bits)
- ppp protocol (16 bits)The goal is to make the following TC command possible:
# tc filter add dev ens6f0 ingress prio 1 protocol ppp_ses \ flower \ pppoe_sid 12 \ ppp_proto ip \ action dropNote that only PPPoE Session is supported.
Signed-off-by Wojciech Drewek <[email protected]>---
v3: revert byte order changes inis_ppp_proto_supportedfrom previous
version, add kernel-doc foris_ppp_proto_supported
v2: use ntohs instead of htons inis_ppp_proto_supportedinclude/net/flow_dissector.h | 11 ++++++++ net/core/flow_dissector.c | 55 ++++++++++++++++++++++++++++++++---- 2 files changed, 60 insertions(+), 6 deletions(-)include/net/flow_dissector.h +0
-0@@ -261,6 +261,16 @@ struct flow_dissector_key_num_of_vlans {u8 num_of_vlans; };
Quoted 11 lines
include/net/flow_dissector.h struct flow_dissector_key_num_of_vlans { · line 272
Quoted 9 lines
include/net/flow_dissector.h +9
-0+/** +* struct flow_dissector_key_pppoe: +* @session_id: pppoe session id +* @ppp_proto: ppp protocol +*/ +struct flow_dissector_key_pppoe { +u16 session_id; +__be16 ppp_proto; +};Why isn't
session_id__be16too?
I've got general impression that storing protocols values
in big endian is a standard through out the code and other values like vlan_id don't have to be stored in big endian, but maybe it's just my illusion :) I can change that in v3.
Quoted 6 lines
Also, I'm not sure I like mixing the PPPoE session ID and PPP protocol fields in the same structure: they're part of two different protocols. However, I can't anticipate any technical problem in doing so, and I guess there's no easy way to let the flow dissector parse the PPP header independently. So well, maybe we don't have choice...
We are not planning to match on other fields from PPP protocol so separate structure just for it is not needed I guess.
Quoted 77 lines
Quoted 61 lines
include/net/flow_dissector.h +1
-0enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CONTROL ,/* struct flow_dissector_key_control */ FLOW_DISSECTOR_KEY_BASIC ,/* struct flow_dissector_key_basic */ @@ -291,6 +301,7 @@ enum flow_dissector_key_id {FLOW_DISSECTOR_KEY_CT ,/* struct flow_dissector_key_ct */ FLOW_DISSECTOR_KEY_HASH ,/* struct flow_dissector_key_hash */ FLOW_DISSECTOR_KEY_NUM_OF_VLANS ,/* struct flow_dissector_key_num_of_vlans */ +FLOW_DISSECTOR_KEY_PPPOE ,/* struct flow_dissector_key_pppoe */ FLOW_DISSECTOR_KEY_MAX, };net/core/flow_dissector.c +33
-1@@ -895,6 +895,39 @@ bool bpf_flow_dissect(struct bpf_prog *prog, struct bpf_flow_dissector *ctx,return result ==BPF_OK ; } +/** +* is_ppp_proto_supported - checks if inner PPP protocol should be dissected +* @proto: protocol type (PPP proto field) +*/ +static bool is_ppp_proto_supported (__be16 proto) +{ +switch (proto) { +case htons (PPP_AT ): +case htons (PPP_IPX ): +case htons (PPP_VJC_COMP ): +case htons (PPP_VJC_UNCOMP ): +case htons (PPP_MP ): +case htons (PPP_COMPFRAG ): +case htons (PPP_COMP ): +case htons (PPP_MPLS_UC ): +case htons (PPP_MPLS_MC ): +case htons (PPP_IPCP ): +case htons (PPP_ATCP ): +case htons (PPP_IPXCP ): +case htons (PPP_IPV6CP ): +case htons (PPP_CCPFRAG ): +case htons (PPP_MPLSCP ): +case htons (PPP_LCP ): +case htons (PPP_PAP ): +case htons (PPP_LQR ): +case htons (PPP_CHAP ): +case htons (PPP_CBCP ): +return true; +default : +return false; + } +} +/** * __skb_flow_dissect - extract the flow_keys struct and return it * @net: associated network namespace, derived from @skb if NULL @@ -1221,19 +1254,29 @@ bool __skb_flow_dissect(const struct net *net, } nhoff +=PPPOE_SES_HLEN ; -switch (hdr->proto) {net/core/flow_dissector.c bool __skb_flow_dissect(const struct net *net, · line 1232
Quoted 10 lines
net/core/flow_dissector.c +2
-4-case htons (PPP_IP ): +if (hdr->proto ==htons (PPP_IP )) { proto =htons (ETH_P_IP ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ; -case htons (PPP_IPV6 ): + }else if (hdr->proto ==htons (PPP_IPV6 )) { proto =htons (ETH_P_IPV6 ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ;1)
Looks like you could easily handle MPLS too. Did you skip it on purpose? (not enough users to justify writing and maintaining the code?).
Quoted 2 lines
I don't mean MPLS has to be supported; I'd just like to know if it was considered.
Yes, exactly as you write, not enough users, but I can see thet MPLS should be easy to implement so I'll include it in the next version.
Quoted 11 lines
2)
Also this whole test is a bit weak: the version, type and code fields must have precise values for the PPPoE Session packet to be valid. If either version or type is different than 1, then the packet advertises a new version of the protocol that we don't know how to parse (or most probably the packet was forged or corrupted). A non-zero code is also invalid.I know the code was already like this before your patch, but it's probably better to fix it before implementing hardware offload.
Sure, I'll add packet validation in next version.
Quoted 5 lines
3)
Finally, the PPP protocol could be compressed and stored in 1 byte instead of 2. This case wasn't handled before your patch, but I think that should be fixed too before implementing hardware offload.
We faced that issue but we couldn't find out what indicates when ppp protocol is stored in 1 byte instead of 2.
Quoted 17 lines
Quoted 17 lines
net/core/flow_dissector.c +12
-1-default : + }else if (is_ppp_proto_supported (hdr->proto)) { + fdret =FLOW_DISSECT_RET_OUT_GOOD ; + }else { fdret =FLOW_DISSECT_RET_OUT_BAD ;break ; } + +if (dissector_uses_key (flow_dissector, +FLOW_DISSECTOR_KEY_PPPOE )) { +struct flow_dissector_key_pppoe *key_pppoe; + + key_pppoe =skb_flow_dissector_target (flow_dissector, +FLOW_DISSECTOR_KEY_PPPOE , + target_container); + key_pppoe->session_id =ntohs (hdr->hdr.sid);
Quoted 8 lines
Quoted 8 lines
net/core/flow_dissector.c +2
-1+ key_pppoe->ppp_proto = hdr->proto; + }break ; }case htons (ETH_P_TIPC ): { --2.35.1
_______________________________________________
Intel-wired-lan mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Re: [RFC PATCH net-next v3 1/4] flow_dissector: Add PPPoE dissectors
Quoted 12 lines · Wojciech
Quoted 11 lines
include/net/flow_dissector.h struct flow_dissector_key_num_of_vlans { · line 272
Quoted 9 lines
include/net/flow_dissector.h +9
-0+/** +* struct flow_dissector_key_pppoe: +* @session_id: pppoe session id +* @ppp_proto: ppp protocol +*/ +struct flow_dissector_key_pppoe { +u16 session_id; +__be16 ppp_proto; +};Why isn't
session_id__be16too?
Quoted 4 lines
I've got general impression that storing protocols values
in big endian is a standard through out the code and other values likevlan_iddon't have to be stored in big endian, but maybe it's just my illusion :) I can change that in v3.
I don't know of any written rule, but looking at other keys, every protocol field is stored with the endianess used on the wire. Only metadata are stored in host byte order. For flow_dissector_key_vlan, vlan_id is a bit special since it's only 12 bits long, but other vlan fields are stored in big endian (vlan_tci is __be16 for example). And vlan ids are special for another reason too: they're also metadata stored in skbuffs because of vlan hardware offload.
But PPPoE Session Id is clearly read from the packet header, where it's stored in network byte order.
Quoted 8 lines
Quoted 5 lines
Also, I'm not sure I like mixing the PPPoE session ID and PPP protocol fields in the same structure: they're part of two different protocols. However, I can't anticipate any technical problem in doing so, and I guess there's no easy way to let the flow dissector parse the PPP header independently. So well, maybe we don't have choice...
We are not planning to match on other fields from PPP protocol so separate structure just for it is not needed I guess.
FTR, I believe it's okay to take this shortcut but for different reasons:
* When transported over PPPoE, PPP frames are not supposed to have address and control fields. Therefore, in this case, the PPP header is limitted to the protocol field, so the dissector key would never have to be extended.
* It's unlikely enough that we'd ever have any other protocol transporting PPP frames to implement in the flow dissector. Therefore, independent PPP dissection code probably won't be needed (even if one wants to add support for L2TP or PPTP in the flow dissector, that probably should be done with tunnel metadata, like VXLAN).
* We have gotos for jumping to "network" or "transport" header dissection (proto_again and ip_proto_again), but no place to restart at the "link" header and no way to tell what type of link layer header we're requesting to parse (Ethernet or PPP).
For all these reasons, I believe your approach is an acceptable shortcut. But I don't buy the "let's limit the flow dissector to what we plan to support in ice" argument.
Quoted 21 lines
Quoted 21 lines
Quoted 5 lines
net/core/flow_dissector.c +0
-1@@ -1221,19 +1254,29 @@ bool __skb_flow_dissect(const struct net *net, } nhoff +=PPPOE_SES_HLEN ; -switch (hdr->proto) {net/core/flow_dissector.c bool __skb_flow_dissect(const struct net *net, · line 1232
Quoted 10 lines
net/core/flow_dissector.c +2
-4-case htons (PPP_IP ): +if (hdr->proto ==htons (PPP_IP )) { proto =htons (ETH_P_IP ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ; -case htons (PPP_IPV6 ): + }else if (hdr->proto ==htons (PPP_IPV6 )) { proto =htons (ETH_P_IPV6 ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ;1)
Looks like you could easily handle MPLS too. Did you skip it on purpose? (not enough users to justify writing and maintaining the code?).
Quoted 5 lines
Quoted 2 lines
I don't mean MPLS has to be supported; I'd just like to know if it was considered.
Yes, exactly as you write, not enough users, but I can see thet MPLS should be easy to implement so I'll include it in the next version.
Okay.
Quoted 8 lines
Quoted 8 lines
2)
Also this whole test is a bit weak: the version, type and code fields must have precise values for the PPPoE Session packet to be valid. If either version or type is different than 1, then the packet advertises a new version of the protocol that we don't know how to parse (or most probably the packet was forged or corrupted). A non-zero code is also invalid.
Quoted 4 lines
Quoted 2 lines
I know the code was already like this before your patch, but it's probably better to fix it before implementing hardware offload.
Sure, I'll add packet validation in next version.
Great!
Quoted 7 lines
Quoted 4 lines
3)
Finally, the PPP protocol could be compressed and stored in 1 byte instead of 2. This case wasn't handled before your patch, but I think that should be fixed too before implementing hardware offload.We faced that issue but we couldn't find out what indicates when ppp protocol is stored in 1 byte instead of 2.
That depends on the least significant bit of the first byte. If it's 0 then the next byte is also part of the protocol field. If it's one, the protocol is "compressed" (that is the high order 0x00 byte has been stripped and we're left with only the least significant byte).
This is explained more formally in RFC 1661 section 2 (PPP Encapsulation):
https://datatracker.ietf.org/doc/html/rfc1661#section-2
and section 6.5 (Protocol-Field-Compression (PFC)):
https://datatracker.ietf.org/doc/html/rfc1661#section-6.5
There should be no reason to use this old PPP feature with PPPoE, but it's still valid (even though it breaks IP header alignment).
RE: [RFC PATCH net-next v3 1/4] flow_dissector: Add PPPoE dissectors
Quoted 40 lines
-----Original Message-----
From: Guillaume Nault <[email protected]>
Sent: piątek, 1 lipca 2022 14:42
To: Drewek, Wojciech <[email protected]>
Cc: Marcin Szycik <[email protected]>; [email protected]; Nguyen, Anthony L <[email protected]>; [email protected]; [email protected]; Brandeburg, Jesse <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Lobakin, Alexandr <[email protected]>; [email protected]; [email protected]
Subject: Re: [RFC PATCH net-next v3 1/4]flow_dissector: Add PPPoE dissectorsQuoted 12 lines · Wojciech
Quoted 11 lines
include/net/flow_dissector.h struct flow_dissector_key_num_of_vlans { · line 272
Quoted 9 lines
include/net/flow_dissector.h +9
-0+/** +* struct flow_dissector_key_pppoe: +* @session_id: pppoe session id +* @ppp_proto: ppp protocol +*/ +struct flow_dissector_key_pppoe { +u16 session_id; +__be16 ppp_proto; +};Why isn't
session_id__be16too?Quoted 4 lines
I've got general impression that storing protocols values
in big endian is a standard through out the code and other values likevlan_iddon't have to be stored in big endian, but maybe it's just my illusion :) I can change that in v3.I don't know of any written rule, but looking at other keys, every protocol field is stored with the endianess used on the wire. Only metadata are stored in host byte order. For
flow_dissector_key_vlan,vlan_idis a bit special since it's only 12 bits long, but other vlan fields are stored in big endian (vlan_tciis__be16for example). And vlan ids are special for another reason too: they're also metadata stored in skbuffs because of vlan hardware offload.
Quoted 2 lines
But PPPoE Session Id is clearly read from the packet header, where it's stored in network byte order.
Thanks for explanation! We'll use __be16 for session_id since now.
Quoted 25 lines
Quoted 9 lines
Quoted 6 lines
Also, I'm not sure I like mixing the PPPoE session ID and PPP protocol fields in the same structure: they're part of two different protocols. However, I can't anticipate any technical problem in doing so, and I guess there's no easy way to let the flow dissector parse the PPP header independently. So well, maybe we don't have choice...
We are not planning to match on other fields from PPP protocol so separate structure just for it is not needed I guess.
FTR, I believe it's okay to take this shortcut but for different reasons:
* When transported over PPPoE, PPP frames are not supposed to have address and control fields. Therefore, in this case, the PPP header is limitted to the protocol field, so the dissector key would never have to be extended.
* It's unlikely enough that we'd ever have any other protocol transporting PPP frames to implement in the flow dissector. Therefore, independent PPP dissection code probably won't be needed (even if one wants to add support for L2TP or PPTP in the flow dissector, that probably should be done with tunnel metadata, like VXLAN).
Quoted 8 lines
* We have gotos for jumping to "network" or "transport" header dissection (
proto_againandip_proto_again), but no place to restart at the "link" header and no way to tell what type of link layer header we're requesting to parse (Ethernet or PPP).For all these reasons, I believe your approach is an acceptable shortcut. But I don't buy the "let's limit the flow dissector to what we plan to support in ice" argument.
Again thanks for explanation. Sorry, I didn't want to suggest that flow_dissector should be designed based only on our needs. We are happy to change our implementation if requested.
We will stay with the current approach if this is the conclusion.
Quoted 58 lines
Quoted 22 lines
Quoted 22 lines
Quoted 6 lines
net/core/flow_dissector.c +0
-1@@ -1221,19 +1254,29 @@ bool __skb_flow_dissect(const struct net *net, } nhoff +=PPPOE_SES_HLEN ; -switch (hdr->proto) {net/core/flow_dissector.c bool __skb_flow_dissect(const struct net *net, · line 1232
Quoted 10 lines
net/core/flow_dissector.c +2
-4-case htons (PPP_IP ): +if (hdr->proto ==htons (PPP_IP )) { proto =htons (ETH_P_IP ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ; -case htons (PPP_IPV6 ): + }else if (hdr->proto ==htons (PPP_IPV6 )) { proto =htons (ETH_P_IPV6 ); fdret =FLOW_DISSECT_RET_PROTO_AGAIN ; -break ;1)
Looks like you could easily handle MPLS too. Did you skip it on purpose? (not enough users to justify writing and maintaining the code?).Quoted 5 lines
Quoted 2 lines
I don't mean MPLS has to be supported; I'd just like to know if it was considered.
Yes, exactly as you write, not enough users, but I can see thet MPLS should be easy to implement so I'll include it in the next version.
Okay.
Quoted 8 lines
Quoted 8 lines
2)
Also this whole test is a bit weak: the version, type and code fields must have precise values for the PPPoE Session packet to be valid. If either version or type is different than 1, then the packet advertises a new version of the protocol that we don't know how to parse (or most probably the packet was forged or corrupted). A non-zero code is also invalid.Quoted 4 lines
Quoted 2 lines
I know the code was already like this before your patch, but it's probably better to fix it before implementing hardware offload.
Sure, I'll add packet validation in next version.
Great!
Quoted 7 lines
Quoted 4 lines
3)
Finally, the PPP protocol could be compressed and stored in 1 byte instead of 2. This case wasn't handled before your patch, but I think that should be fixed too before implementing hardware offload.We faced that issue but we couldn't find out what indicates when ppp protocol is stored in 1 byte instead of 2.
That depends on the least significant bit of the first byte. If it's 0 then the next byte is also part of the protocol field. If it's one, the protocol is "compressed" (that is the high order
0x00byte has been stripped and we're left with only the least significant byte).
Quoted 8 lines
This is explained more formally in RFC 1661 section 2 (PPP Encapsulation):
https://datatracker.ietf.org/doc/html/rfc1661#section-2and section 6.5 (Protocol-Field-Compression (PFC)):
https://datatracker.ietf.org/doc/html/rfc1661#section-6.5There should be no reason to use this old PPP feature with PPPoE, but it's still valid (even though it breaks IP header alignment).
Thanks for explanation! From the next version we will support both options.
_______________________________________________
Intel-wired-lan mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
RFC PATCH v3 2/4 net/sched: flower: Add PPPoE filter
In reply to Marcin SzycikFrom: Wojciech Drewek <[email protected]>
Add support for PPPoE specific fields for tc-flower. Those fields can be provided only when protocol was set to ETH_P_PPP_SES. Defines, dump, load and set are being done here.
Overwrite basic.n_proto only in case of PPP_IP and PPP_IPV6, otherwise leave it as ETH_P_PPP_SES.
--- include/uapi/linux/pkt_cls.h | 3 +++ net/sched/cls_flower.c | 46 ++++++++++++++++++++++++++++++++++++ 2 files changed, 49 insertions(+)
include/uapi/linux/pkt_cls.h +3 -0
@@ -589,6 +589,9 @@ enum {TCA_FLOWER_KEY_NUM_OF_VLANS ,/* u8 */ +TCA_FLOWER_KEY_PPPOE_SID ,/* u16 */ +TCA_FLOWER_KEY_PPP_PROTO ,/* be16 */ + __TCA_FLOWER_MAX, };
net/sched/cls_flower.c +46 -0
88 lines not on this page · raw message
Signature · 6 lines
2.35.1 _______________________________________________ Intel-wired-lan mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Re: [RFC PATCH net-next v3 2/4] net/sched: flower: Add PPPoE filter
Quoted 20 lines · Marcin Szycik
From: Wojciech Drewek <[email protected]>
Add support for PPPoE specific fields for tc-flower. Those fields can be provided only when protocol was set to
ETH_P_PPP_SES. Defines, dump, load and set are being done here.Overwrite basic.n_proto only in case of
PPP_IPandPPP_IPV6, otherwise leave it asETH_P_PPP_SES.Signed-off-by Wojciech Drewek <[email protected]>--- include/uapi/linux/pkt_cls.h | 3 +++ net/sched/cls_flower.c | 46 ++++++++++++++++++++++++++++++++++++ 2 files changed, 49 insertions(+)include/uapi/linux/pkt_cls.h +0
-0
include/uapi/linux/pkt_cls.h enum { · line 593
Quoted 5 lines
include/uapi/linux/pkt_cls.h +2
-0@@ -589,6 +589,9 @@ enum {TCA_FLOWER_KEY_NUM_OF_VLANS ,/* u8 */ +TCA_FLOWER_KEY_PPPOE_SID ,/* u16 */ + TCA_FLOWER_KEY_PPP_PROTO, /* be16 */
Same as for patch 1, should PPPOE_SID be a be16?
Quoted 49 lines
include/uapi/linux/pkt_cls.h +0
-0__TCA_FLOWER_MAX, };net/sched/cls_flower.c +17
-0@@ -16,6 +16,7 @@#include <linux/in6.h> #include <linux/ip.h> #include <linux/mpls.h> +#include <linux/ppp_defs.h> #include <net/sch_generic.h> #include <net/pkt_cls.h> @@ -73,6 +74,7 @@ struct fl_flow_key {struct flow_dissector_key_ct ct;struct flow_dissector_key_hash hash;struct flow_dissector_key_num_of_vlans num_of_vlans; +struct flow_dissector_key_pppoe pppoe; }__aligned(BITS_PER_LONG / 8) ;/* Ensure that we can do comparisons as longs. */ struct fl_flow_mask_range {@@ -714,6 +716,8 @@ static const struct nla_policy fl_policy[TCA_FLOWER_MAX + 1] = { [TCA_FLOWER_KEY_HASH] = { .type = NLA_U32 }, [TCA_FLOWER_KEY_HASH_MASK] = { .type = NLA_U32 }, [TCA_FLOWER_KEY_NUM_OF_VLANS] = { .type = NLA_U8 }, + [TCA_FLOWER_KEY_PPPOE_SID] = { .type = NLA_U16 }, + [TCA_FLOWER_KEY_PPP_PROTO] = { .type = NLA_U16 }, };@@ -1041,6 +1045,32 @@ static void fl_set_key_vlan(struct nlattr **tb, } } +static void fl_set_key_pppoe (struct nlattr **tb, +struct flow_dissector_key_pppoe *key_val, +struct flow_dissector_key_pppoe *key_mask, +struct fl_flow_key *key, +struct fl_flow_key *mask) +{ +if (tb[TCA_FLOWER_KEY_PPPOE_SID ]) { + key_val->session_id = +nla_get_u16 (tb[TCA_FLOWER_KEY_PPPOE_SID ]); + key_mask->session_id =0xffff ; + } +if (tb[TCA_FLOWER_KEY_PPP_PROTO ]) { + key_val->ppp_proto =
net/sched/cls_flower.c static void fl_set_key_vlan(struct nlattr **tb, · line 1070
Quoted 10 lines
net/sched/cls_flower.c +10
-0+nla_get_be16 (tb[TCA_FLOWER_KEY_PPP_PROTO ]); + key_mask->ppp_proto =cpu_to_be16 (~0 ); + +if (key_val->ppp_proto ==htons (PPP_IP )) { + key->basic.n_proto =htons (ETH_P_IP ); + mask->basic.n_proto =cpu_to_be16 (~0 ); + }else if (key_val->ppp_proto ==htons (PPP_IPV6 )) { + key->basic.n_proto =htons (ETH_P_IPV6 ); + mask->basic.n_proto =cpu_to_be16 (~0 ); + }
Again, is the lack of MPLS support voluntary?
Quoted 46 lines
net/sched/cls_flower.c +19
-0+ } +} +static void fl_set_key_flag (u32 flower_key,u32 flower_mask,u32 *dissector_key,u32 *dissector_mask,u32 flower_flag_bit,u32 dissector_flag_bit)@@ -1651,6 +1681,9 @@ static int fl_set_key(struct net *net, struct nlattr **tb, } } +if (key->basic.n_proto ==htons (ETH_P_PPP_SES )) +fl_set_key_pppoe (tb, &key->pppoe, &mask->pppoe, key, mask); +if (key->basic.n_proto ==htons (ETH_P_IP ) || key->basic.n_proto ==htons (ETH_P_IPV6 )) { fl_set_key_val(tb, &key->basic.ip_proto, TCA_FLOWER_KEY_IP_PROTO,@@ -1923,6 +1956,8 @@ static void fl_init_dissector(struct flow_dissector *dissector, FLOW_DISSECTOR_KEY_HASH, hash);FL_KEY_SET_IF_MASKED (mask, keys, cnt,FLOW_DISSECTOR_KEY_NUM_OF_VLANS , num_of_vlans); +FL_KEY_SET_IF_MASKED (mask, keys, cnt, +FLOW_DISSECTOR_KEY_PPPOE , pppoe);skb_flow_dissector_init (dissector, keys, cnt); }@@ -3051,6 +3086,17 @@ static int fl_dump_key(struct sk_buff *skb, struct net *net, fl_dump_key_ip(skb, false, &key->ip, &mask->ip))) goto nla_put_failure; +if (mask->pppoe.session_id) { +if (nla_put_u16 (skb,TCA_FLOWER_KEY_PPPOE_SID , + key->pppoe.session_id)) + goto nla_put_failure; + } +if (mask->basic.n_proto && mask->pppoe.ppp_proto) { +if (nla_put_be16 (skb,TCA_FLOWER_KEY_PPP_PROTO , + key->pppoe.ppp_proto)) + goto nla_put_failure; + } + if (key->control.addr_type == FLOW_DISSECTOR_KEY_IPV4_ADDRS && (fl_dump_key_val(skb, &key->ipv4.src, TCA_FLOWER_KEY_IPV4_SRC, &mask->ipv4.src, TCA_FLOWER_KEY_IPV4_SRC_MASK,Signature · 1 line
2.35.1
RFC PATCH v3 3/4 flow_offload: Introduce flow_match_pppoe
In reply to Marcin SzycikFrom: Wojciech Drewek <[email protected]>
Allow to offload PPPoE filters by adding flow_rule_match_pppoe. Drivers can extract PPPoE specific fields from now on.
--- include/net/flow_offload.h | 6 ++++++ net/core/flow_offload.c | 7 +++++++ 2 files changed, 13 insertions(+)
include/net/flow_offload.h +6 -0
@@ -72,6 +72,10 @@ struct flow_match_ct {struct flow_dissector_key_ct *key, *mask; }; +struct flow_match_pppoe { +struct flow_dissector_key_pppoe *key, *mask; +}; +struct flow_rule ; void flow_rule_match_meta(const struct flow_rule *rule,
@@ -116,6 +120,8 @@ void flow_rule_match_enc_opts(const struct flow_rule *rule, struct flow_match_enc_opts *out);void flow_rule_match_ct (const struct flow_rule *rule,struct flow_match_ct *out); +void flow_rule_match_pppoe (const struct flow_rule *rule, +struct flow_match_pppoe *out);enum flow_action_id {FLOW_ACTION_ACCEPT =0 ,
net/core/flow_offload.c +7 -0
@@ -223,6 +223,13 @@ void flow_rule_match_ct(const struct flow_rule *rule, }EXPORT_SYMBOL (flow_rule_match_ct); +void flow_rule_match_pppoe (const struct flow_rule *rule, +struct flow_match_pppoe *out) +{ +FLOW_DISSECTOR_MATCH (rule,FLOW_DISSECTOR_KEY_PPPOE , out); +} +EXPORT_SYMBOL (flow_rule_match_pppoe); +struct flow_block_cb *flow_block_cb_alloc (flow_setup_cb_t *cb,void *cb_ident,void *cb_priv,void (*release)(void *cb_priv))
Signature · 1 line
2.35.1
RFC PATCH v3 4/4 ice: Add support for PPPoE hardware offload
In reply to Marcin SzycikAdd support for creating PPPoE filters in switchdev mode. Add support for parsing PPPoE and PPP-specific tc options: pppoe_sid and ppp_proto.
Example filter:
tc filter add dev $PF1 ingress protocol ppp_ses prio 1 flower pppoe_sid \
1234 ppp_proto ip skip_sw action mirred egress redirect dev $VF1_PR
Changes in iproute2 are required to use the new fields.
ICE COMMS DDP package is required to create a filter as it contains PPPoE profiles. Added a warning message when loaded DDP package does not contain required profiles.
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
[0] https://patchwork.ozlabs.org/project/intel-wired-lan/patch/[email protected]
---
v2: wrap one long line
drivers/net/ethernet/intel/ice/ice.h | 1 + .../net/ethernet/intel/ice/ice_flex_pipe.c | 5 +- .../ethernet/intel/ice/ice_protocol_type.h | 11 ++ drivers/net/ethernet/intel/ice/ice_switch.c | 165 ++++++++++++++++++ drivers/net/ethernet/intel/ice/ice_tc_lib.c | 95 ++++++++-- drivers/net/ethernet/intel/ice/ice_tc_lib.h | 8 + 6 files changed, 274 insertions(+), 11 deletions(-)
drivers/net/ethernet/intel/ice/ice.h +1 -0
@@ -52,6 +52,7 @@#include <net/udp_tunnel.h> #include <net/vxlan.h> #include <net/gtp.h> +#include <linux/ppp_defs.h> #include "ice_devids.h" #include "ice_type.h" #include "ice_txrx.h"
drivers/net/ethernet/intel/ice/ice_flex_pipe.c +4 -1
@@ -1964,8 +1964,11 @@ ice_get_sw_fv_list(struct ice_hw *hw, struct ice_prot_lkup_ext *lkups, } } }while (fv); -if (list_empty (fv_list)) +if (list_empty (fv_list)) { +dev_warn (ice_hw_to_dev (hw),"Required profiles not found in currently loaded DDP package" );return -EIO ; + } +return 0 ; err:
drivers/net/ethernet/intel/ice/ice_protocol_type.h +11 -0
@@ -43,6 +43,7 @@ enum ice_protocol_type {ICE_NVGRE ,ICE_GTP ,ICE_GTP_NO_PAY , +ICE_PPPOE ,ICE_VXLAN_GPE ,ICE_SCTP_IL ,ICE_PROTOCOL_LAST
@@ -107,6 +108,7 @@ enum ice_prot_id {#define ICE_TCP_IL_HW 49#define ICE_UDP_ILOS_HW 53#define ICE_GRE_OF_HW 64 +#define ICE_PPPOE_HW 103#define ICE_UDP_OF_HW 52/* UDP Tunnels */ #define ICE_META_DATA_ID_HW 255/* this is used for tunnel type */
@@ -200,6 +202,14 @@ struct ice_udp_gtp_hdr {u8 rsvrd; }; +struct ice_pppoe_hdr { +u8 rsrvd_ver_type; +u8 rsrvd_code; +__be16 session_id; +__be16 length; +__be16 ppp_prot_id;/* control and data only */ +}; +struct ice_nvgre_hdr {__be16 flags;__be16 protocol;
@@ -217,6 +227,7 @@ union ice_prot_hdr {struct ice_udp_tnl_hdr tnl_hdr;struct ice_nvgre_hdr nvgre_hdr;struct ice_udp_gtp_hdr gtp_hdr; +struct ice_pppoe_hdr pppoe_hdr; };/* This is mapping table entry that maps every word within a given protocol
drivers/net/ethernet/intel/ice/ice_switch.c +165 -0
207 lines not on this page · raw message
drivers/net/ethernet/intel/ice/ice_tc_lib.c +85 -10
137 lines not on this page · raw message
drivers/net/ethernet/intel/ice/ice_tc_lib.h +8 -0
@@ -23,6 +23,8 @@#define ICE_TC_FLWR_FIELD_ENC_DST_MAC BIT(16)#define ICE_TC_FLWR_FIELD_ETH_TYPE_ID BIT(17)#define ICE_TC_FLWR_FIELD_ENC_OPTS BIT(18) +#define ICE_TC_FLWR_FIELD_PPPOE_SESSID BIT(19) +#define ICE_TC_FLWR_FIELD_PPP_PROTO BIT(20)#define ICE_TC_FLOWER_MASK_32 0xFFFFFFFF
@@ -42,6 +44,11 @@ struct ice_tc_vlan_hdr {u16 vlan_prio;/* Only last 3 bits valid (valid values: 0..7) */ }; +struct ice_tc_pppoe_hdr { +__be16 session_id; +__be16 ppp_proto; +}; +struct ice_tc_l2_hdr {u8 dst_mac[ETH_ALEN ];u8 src_mac[ETH_ALEN ];
@@ -81,6 +88,7 @@ struct ice_tc_flower_lyr_2_4_hdrs {struct ice_tc_l2_hdr l2_key;struct ice_tc_l2_hdr l2_mask;struct ice_tc_vlan_hdr vlan_hdr; +struct ice_tc_pppoe_hdr pppoe_hdr;/* L3 (IPv4[6]) layer fields with their mask */ struct ice_tc_l3_hdr l3_key;struct ice_tc_l3_hdr l3_mask;
Signature · 1 line
2.35.1
Re: [RFC PATCH net-next v3 4/4] ice: Add support for PPPoE hardware offload
Quoted 9 lines · Marcin Szycik
Add support for creating PPPoE filters in switchdev mode. Add support for parsing PPPoE and PPP-specific tc options:
pppoe_sidandppp_proto.Example filter:
tc filter add dev $PF1 ingress protocolppp_sesprio 1 flowerpppoe_sid\
1234ppp_protoipskip_swaction mirred egress redirect dev $VF1_PRChanges in iproute2 are required to use the new fields.
Quoted 8 lines
ICE COMMS DDP package is required to create a filter as it contains PPPoE profiles. Added a warning message when loaded DDP package does not contain required profiles.
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
[0] https://patchwork.ozlabs.org/project/intel-wired-lan/patch/[email protected]
Out of curiosity, can ice direct PPPoE Session packets to different queues with RSS (based on the session ID)?
Re: [RFC PATCH net-next v3 4/4] ice: Add support for PPPoE hardware offload
Quoted 14 lines · Guillaume Nault
Quoted 13 lines · Marcin Szycik
Add support for creating PPPoE filters in switchdev mode. Add support for parsing PPPoE and PPP-specific tc options:
pppoe_sidandppp_proto.Example filter:
tc filter add dev $PF1 ingress protocolppp_sesprio 1 flowerpppoe_sid\
1234ppp_protoipskip_swaction mirred egress redirect dev $VF1_PRChanges in iproute2 are required to use the new fields.
ICE COMMS DDP package is required to create a filter as it contains PPPoE profiles. Added a warning message when loaded DDP package does not contain required profiles.
Quoted 7 lines
Quoted 4 lines
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
[0] https://patchwork.ozlabs.org/project/intel-wired-lan/patch/[email protected]
Out of curiosity, can ice direct PPPoE Session packets to different queues with RSS (based on the session ID)?
Hardware should support it, but I'm not sure if it's possible with the current driver and how to configure it. I'll try to find out.
_______________________________________________
Intel-wired-lan mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Re: [RFC PATCH net-next v3 4/4] ice: Add support for PPPoE hardware offload
Quoted 20 lines · Marcin Szycik
Quoted 17 lines · Guillaume Nault
Quoted 16 lines · Marcin Szycik
Add support for creating PPPoE filters in switchdev mode. Add support for parsing PPPoE and PPP-specific tc options:
pppoe_sidandppp_proto.Example filter:
tc filter add dev $PF1 ingress protocolppp_sesprio 1 flowerpppoe_sid\
1234ppp_protoipskip_swaction mirred egress redirect dev $VF1_PRChanges in iproute2 are required to use the new fields.
ICE COMMS DDP package is required to create a filter as it contains PPPoE profiles. Added a warning message when loaded DDP package does not contain required profiles.
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
Quoted 6 lines
Quoted 4 lines
Out of curiosity, can ice direct PPPoE Session packets to different queues with RSS (based on the session ID)?
Hardware should support it, but I'm not sure if it's possible with the current driver and how to configure it. I'll try to find out.
From what I understand, currently it's not possible to configure RSS for PPPoE session id, because ethtool does not support PPPoE.
_______________________________________________
Intel-wired-lan mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
Re: [RFC PATCH net-next v3 4/4] ice: Add support for PPPoE hardware offload
Quoted 23 lines · Marcin Szycik
Quoted 20 lines · Marcin Szycik
Quoted 17 lines · Guillaume Nault
Quoted 16 lines · Marcin Szycik
Add support for creating PPPoE filters in switchdev mode. Add support for parsing PPPoE and PPP-specific tc options:
pppoe_sidandppp_proto.Example filter:
tc filter add dev $PF1 ingress protocolppp_sesprio 1 flowerpppoe_sid\
1234ppp_protoipskip_swaction mirred egress redirect dev $VF1_PRChanges in iproute2 are required to use the new fields.
ICE COMMS DDP package is required to create a filter as it contains PPPoE profiles. Added a warning message when loaded DDP package does not contain required profiles.
Note: currently matching on vlan + PPPoE fields is not supported. Patch [0] will add this feature.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Out of curiosity, can ice direct PPPoE Session packets to different queues with RSS (based on the session ID)?
Hardware should support it, but I'm not sure if it's possible with the current driver and how to configure it. I'll try to find out.
From what I understand, currently it's not possible to configure RSS for PPPoE session id, because ethtool does not support PPPoE.
Thanks, that's interesting. PPPoE support in RSS would have been useful to me a few years ago. I've heard some former collegues tried to use eBPF to work around this limitation and spread packets to different cores.