netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Qingfang Deng <dqfext@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [RFC PATCH net-next] net: ppp: convert to IFF_NO_QUEUE
Date: Thu, 7 Nov 2024 14:51:24 +0000	[thread overview]
Message-ID: <20241107145124.GW4507@kernel.org> (raw)
In-Reply-To: <87pln99a28.fsf@toke.dk>

On Tue, Nov 05, 2024 at 12:47:27PM +0100, Toke Høiland-Jørgensen wrote:
> Simon Horman <horms@kernel.org> writes:
> 
> > + Toke
> >
> > On Tue, Oct 29, 2024 at 06:36:56PM +0800, Qingfang Deng wrote:
> >> When testing the parallel TX performance of a single PPPoE interface
> >> over a 2.5GbE link with multiple hardware queues, the throughput could
> >> not exceed 1.9Gbps, even with low CPU usage.
> >> 
> >> This issue arises because the PPP interface is registered with a single
> >> queue and a tx_queue_len of 3. This default behavior dates back to Linux
> >> 2.3.13, which was suitable for slower serial ports. However, in modern
> >> devices with multiple processors and hardware queues, this configuration
> >> can lead to congestion.
> >> 
> >> For PPPoE/PPTP, the lower interface should handle qdisc, so we need to
> >> set IFF_NO_QUEUE. For PPP over a serial port, we don't benefit from a
> >> qdisc with such a short TX queue, so handling TX queueing in the driver
> >> and setting IFF_NO_QUEUE is more effective.
> >> 
> >> With this change, PPPoE interfaces can now fully saturate a 2.5GbE link.
> >> 
> >> Signed-off-by: Qingfang Deng <dqfext@gmail.com>
> >
> > Hi Toke,
> >
> > I'm wondering if you could offer an opinion on this.
> 
> Hi Simon
> 
> Thanks for bringing this to my attention; I'll reply to the parent
> directly :)

Likewise, thanks for following-up on this.

  reply	other threads:[~2024-11-07 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 10:36 [RFC PATCH net-next] net: ppp: convert to IFF_NO_QUEUE Qingfang Deng
2024-11-04 11:50 ` Simon Horman
2024-11-05 11:47   ` Toke Høiland-Jørgensen
2024-11-07 14:51     ` Simon Horman [this message]
2024-11-05 12:23 ` Toke Høiland-Jørgensen
2024-11-05 14:25   ` Qingfang Deng
2024-11-05 14:35     ` Toke Høiland-Jørgensen
2024-11-05 15:04       ` Qingfang Deng

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=20241107145124.GW4507@kernel.org \
    --to=horms@kernel.org \
    --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=pabeni@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).