From: Paolo Abeni <pabeni@redhat.com>
To: Qingfang Deng <dqfext@gmail.com>
Cc: "Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [PATCH net-next v4] ppp: enable TX scatter-gather
Date: Tue, 3 Feb 2026 17:33:24 +0100 [thread overview]
Message-ID: <fee77ae1-0231-414f-be43-6dca8bdb0e20@redhat.com> (raw)
In-Reply-To: <CALW65jYYdX+NQ-6vNBdxDGHxDV1AdKQWenFZNjnqE9VQyC7fog@mail.gmail.com>
On 2/3/26 4:08 PM, Qingfang Deng wrote:
> On Tue, Feb 3, 2026 at 6:55 PM Paolo Abeni <pabeni@redhat.com> wrote:
>> I'm sorry for missing this point before, but AFAICS channels with
>> chan->direct_xmit == 0 do not support GSO packets at all, and here such
>> packets will be transmitted after linearization (but still as GSO).
>>
>> I think that while transmitting over !chan->direct_xmit you additionally
>> need to check for GSO packet. If ppp features are recomputed depending
>> on the channels configuration, you could chose to drop such packets.
>> Otherwise you will need to segment them before transmission, and that
>> looks error prone in case of multilink.
>
> I don't think that's true. Using the current features set (NETIF_F_SG
> | NETIF_F_FRAGLIST), the network core will only enable the generic
> software GSO (NETIF_F_GSO), and a GSO skb will be segmented in
> validate_xmit_skb before being passed to the PPP driver.
Right you are! I thought TSO was enabled here at some point but it's not
the case. No need to resubmit, let me resurrect this patch in PW.
Thanks,
Paolo
next prev parent reply other threads:[~2026-02-03 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 1:29 [PATCH net-next v4] ppp: enable TX scatter-gather Qingfang Deng
2026-02-03 10:55 ` Paolo Abeni
2026-02-03 15:08 ` Qingfang Deng
2026-02-03 16:33 ` Paolo Abeni [this message]
2026-02-05 9:20 ` patchwork-bot+netdevbpf
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=fee77ae1-0231-414f-be43-6dca8bdb0e20@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox