From: Qingfang Deng <qingfang.deng@linux.dev>
To: "Pali Rohár" <pali@kernel.org>
Cc: Guillaume Nault <gnault@redhat.com>,
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>,
Kees Cook <kees@kernel.org>,
Asim Viladi Oglu Manizada <manizada@pm.me>,
Eric Woudstra <ericwouds@gmail.com>, Felix Fietkau <nbd@nbd.name>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@ozlabs.org>,
Michal Ostrowski <mostrows@gmail.com>
Subject: Re: [RFC net-next] pppoe: remove session socket receive support
Date: Mon, 10 Aug 2026 10:28:02 +0800 [thread overview]
Message-ID: <26e0b578-0f8f-49f6-aaa6-b814c89ebe3f@linux.dev> (raw)
In-Reply-To: <20260809225954.i36fajv6twbnjfdp@pali>
On 2026/8/10 6:59, Pali Rohár wrote:
> I see. Maybe you could ask developers of the first version of driver if
> they remember something. But probably nobody would remember old things.
I wish I could, but the maintainer of PPPoX has gone AWOL for quite a
long time.. (commit 2fd68c7ea2ae)
> Clearing the queue after the transition happens sounds like a good idea.
> If I understand correctly, it does not make sense to get packets into
> userspace once the socket is bound to PPP layer.
>
> I have feeling that kernel PPP layer and its API do fully fit into the
> API for network devices and netlink layer for userspace.
prev parent reply other threads:[~2026-08-10 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 9:16 [RFC net-next] pppoe: remove session socket receive support Qingfang Deng
2026-08-09 14:58 ` Pali Rohár
2026-08-09 16:17 ` Qingfang Deng
2026-08-09 22:59 ` Pali Rohár
2026-08-10 2:28 ` Qingfang Deng [this message]
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=26e0b578-0f8f-49f6-aaa6-b814c89ebe3f@linux.dev \
--to=qingfang.deng@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--cc=gnault@redhat.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manizada@pm.me \
--cc=mostrows@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pali@kernel.org \
--cc=paulus@ozlabs.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