[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87bjum1anl.fsf@toke.dk>
Date: Fri, 28 Feb 2025 14:06:22 +0100
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Qingfang Deng <dqfext@...il.com>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Michal Ostrowski <mostrows@...thlink.net>, James
Chapman <jchapman@...alix.com>, Simon Horman <horms@...nel.org>,
linux-ppp@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH net-next v3] ppp: use IFF_NO_QUEUE in virtual
interfaces
Qingfang Deng <dqfext@...il.com> writes:
> For PPPoE, PPTP, and PPPoL2TP, the start_xmit() function directly
> forwards packets to the underlying network stack and never returns
> anything other than 1. So these interfaces do not require a qdisc,
> and the IFF_NO_QUEUE flag should be set.
>
> Introduces a direct_xmit flag in struct ppp_channel to indicate when
> IFF_NO_QUEUE should be applied. The flag is set in ppp_connect_channel()
> for relevant protocols.
>
> Signed-off-by: Qingfang Deng <dqfext@...il.com>
> ---
> v3:
> Move direct_xmit above the unused "latency" member to avoid
> confusion. Should I remove it instead?
If it really is unused, I think removing it is better to remove it,
yeah :)
-Toke
Powered by blists - more mailing lists