From: Qingfang Deng <dqfext@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Guillaume Nault <gnault@redhat.com>
Subject: [PATCH net-next 0/3] ppp: improve receive path performance
Date: Wed, 25 Jun 2025 11:40:17 +0800 [thread overview]
Message-ID: <20250625034021.3650359-1-dqfext@gmail.com> (raw)
This patch series improves the performance of the PPPoE receive paths.
Patch 1 converts the ppp->rlock from a spinlock to a read-write lock,
allowing concurrent receive-side processing when no state is being
modified.
Patch 2 optimizes PPPoE receive performance by bypassing sk_receive_skb()
when the socket is in the PPPOX_BOUND state, avoiding unnecessary socket
locking and overhead.
Patch 3 synchronizes all updates to net_device->stats using
DEV_STATS_INC() to prevent data races now that the receive path may run on
multiple CPUs.
Qingfang Deng (3):
ppp: convert rlock to rwlock to improve RX concurrency
pppoe: call ppp_input directly when PPPOX_BOUND
ppp: synchronize netstats updates
drivers/net/ppp/ppp_generic.c | 32 +++++++++++++++++---------------
drivers/net/ppp/pppoe.c | 10 +++++++++-
2 files changed, 26 insertions(+), 16 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-25 3:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 3:40 Qingfang Deng [this message]
2025-06-25 3:40 ` [PATCH net-next 1/3] ppp: convert rlock to rwlock to improve RX concurrency Qingfang Deng
2025-06-25 8:11 ` Andrew Lunn
2025-06-26 16:23 ` Guillaume Nault
2025-06-27 3:58 ` Qingfang Deng
2025-06-27 6:44 ` Eric Dumazet
2025-06-27 9:23 ` Qingfang Deng
2025-06-25 3:40 ` [PATCH net-next 2/3] pppoe: bypass sk_receive_skb for PPPOX_BOUND sockets Qingfang Deng
2025-06-25 3:40 ` [PATCH net-next 3/3] ppp: synchronize netstats updates Qingfang Deng
2025-06-25 8:16 ` Andrew Lunn
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=20250625034021.3650359-1-dqfext@gmail.com \
--to=dqfext@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--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 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®