From: Paolo Abeni <pabeni@redhat.com>
To: Felix Fietkau <nbd@nbd.name>,
netdev@vger.kernel.org, Michal Ostrowski <mostrows@earthlink.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: pppoe: implement GRO support
Date: Tue, 22 Jul 2025 10:36:31 +0200 [thread overview]
Message-ID: <5f250beb-6a81-42b2-bf6f-da02c04cbf15@redhat.com> (raw)
In-Reply-To: <20250716081441.93088-1-nbd@nbd.name>
On 7/16/25 10:14 AM, Felix Fietkau wrote:
> +static struct sk_buff *pppoe_gro_receive(struct list_head *head,
> + struct sk_buff *skb)
> +{
> + const struct packet_offload *ptype;
> + unsigned int hlen, off_pppoe;
> + struct sk_buff *pp = NULL;
> + struct pppoe_hdr *phdr;
> + struct sk_buff *p;
> + __be16 type;
> + int flush = 1;
Minor nit: please respect the reverse christmas tree order above
> + off_pppoe = skb_gro_offset(skb);
> + hlen = off_pppoe + sizeof(*phdr) + 2;
> + phdr = skb_gro_header(skb, hlen, off_pppoe);
> + if (unlikely(!phdr))
> + goto out;
> +
> + /* ignore packets with padding or invalid length */
> + if (skb_gro_len(skb) != be16_to_cpu(phdr->length) + hlen - 2)
> + goto out;
> +
> + NAPI_GRO_CB(skb)->network_offsets[NAPI_GRO_CB(skb)->encap_mark] = hlen;
> +
> + type = pppoe_hdr_proto(phdr);
> + if (!type)
> + goto out;
> +
> + ptype = gro_find_receive_by_type(type);
> + if (!ptype)
> + goto out;
> +
> + flush = 0;
> +
> + list_for_each_entry(p, head, list) {
> + struct pppoe_hdr *phdr2;
> +
> + if (!NAPI_GRO_CB(p)->same_flow)
> + continue;
> +
> + phdr2 = (struct pppoe_hdr *)(p->data + off_pppoe);
> + if (compare_pppoe_header(phdr, phdr2))
> + NAPI_GRO_CB(p)->same_flow = 0;
> + }
> +
> + skb_gro_pull(skb, sizeof(*phdr) + 2);
> + skb_gro_postpull_rcsum(skb, phdr, sizeof(*phdr) + 2);
> +
> + pp = ptype->callbacks.gro_receive(head, skb);
Here you can use INDIRECT_CALL_INET()
> +
> +out:
> + skb_gro_flush_final(skb, pp, flush);
> +
> + return pp;
> +}
> +
> +static int pppoe_gro_complete(struct sk_buff *skb, int nhoff)
> +{
> + struct pppoe_hdr *phdr = (struct pppoe_hdr *)(skb->data + nhoff);
> + __be16 type = pppoe_hdr_proto(phdr);
> + struct packet_offload *ptype;
> + int err = -ENOENT;
> +
> + ptype = gro_find_complete_by_type(type);
> + if (ptype)
> + err = ptype->callbacks.gro_complete(skb, nhoff +
> + sizeof(*phdr) + 2);
Possibly even here but it's less relevant.
> +
> + return err;
> +}
> +
> +static struct packet_offload pppoe_packet_offload __read_mostly = {
> + .type = cpu_to_be16(ETH_P_PPP_SES),
> + .priority = 10,
The priority value should be IMHO greater then the exiting ones to avoid
possible regressions on other protocols. i.e. 20 should do.
Thanks,
Paolo
next prev parent reply other threads:[~2025-07-22 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 8:14 Felix Fietkau
2025-07-22 8:36 ` Paolo Abeni [this message]
2025-07-22 8:56 ` Felix Fietkau
2025-07-25 12:42 ` Alexander Lobakin
2025-07-25 12:54 ` Paolo Abeni
2025-07-22 14:04 ` Eric Dumazet
2025-07-22 14:47 ` Paolo Abeni
2025-07-22 14:56 ` Felix Fietkau
2025-07-31 14:08 ` Richard Gobert
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=5f250beb-6a81-42b2-bf6f-da02c04cbf15@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mostrows@earthlink.net \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.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 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®