From: "Pali Rohár" <pali@kernel.org>
To: Guillaume Nault <gnault@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Paul Mackerras <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
linux-ppp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppp: Add rtnl attribute IFLA_PPP_UNIT_ID for specifying ppp unit id
Date: Tue, 10 Aug 2021 16:04:50 +0000 [thread overview]
Message-ID: <20210810160450.eluiktsp7oentxo3@pali> (raw)
In-Reply-To: <20210810153941.GB14279@pc-32.home>
On Tuesday 10 August 2021 17:39:41 Guillaume Nault wrote:
> On Mon, Aug 09, 2021 at 09:31:09PM +0200, Pali Rohár wrote:
> > Better to wait. I would like hear some comments / review on this patch
> > if this is the correct approach as it adds a new API/ABI for userspace.
>
> Personally I don't understand the use case for setting the ppp unit at
> creation time.
I know about two use cases:
* ppp unit id is used for generating network interface name. So if you
want interface name ppp10 then you request for unit id 10. It is
somehow common that when ppp interface has prefix "ppp" in its name
then it is followed by unit id. Seems that existing ppp applications
which use "ppp<num>" naming expects this. But of course you do not
have to use this convention and rename interfaces as you want.
* Some of ppp ioctls use unit id. So you may want to use some specific
number for some network interface. So e.g. unit id 1 will be always
for /dev/ttyUSB1.
> I didn't implement it on purpose when creating the
> netlink interface, as I didn't have any use case.
>
> On the other hand, adding the ppp unit in the netlink dump is probably
> useful.
Yes, this could be really useful as currently if you ask netlink to
create a new ppp interface you have to use ioctl to retrieve this unit
id. But ppp currently does not provide netlink dump operation.
Also it could be useful for this "bug":
https://lore.kernel.org/netdev/20210807132703.26303-1-pali@kernel.org/t/#u
And with unit id there also another issue:
https://lore.kernel.org/netdev/20210807160050.17687-1-pali@kernel.org/t/#u
But due to how it is used we probably have to deal with it how ppp unit
id are defined and assigned...
next prev parent reply other threads:[~2021-08-10 16:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 16:37 [PATCH] ppp: Add rtnl attribute IFLA_PPP_UNIT_ID for specifying ppp unit id Pali Rohár
2021-08-09 19:25 ` Jakub Kicinski
2021-08-09 19:31 ` Pali Rohár
2021-08-10 15:39 ` Guillaume Nault
2021-08-10 16:04 ` Pali Rohár [this message]
2021-08-11 17:19 ` Guillaume Nault
2021-08-11 17:54 ` Pali Rohár
2021-08-12 9:19 ` Guillaume Nault
2021-08-12 14:09 ` Pali Rohár
2021-08-12 19:12 ` Guillaume Nault
[not found] ` <BN0P223MB0327A247724B7AE211D2E84EA7F79@BN0P223MB0327.NAMP223.PROD.OUTLOOK.COM>
2021-08-10 17:16 ` Pali Rohár
2021-08-10 18:11 ` James Carlson
2021-08-11 17:38 ` Guillaume Nault
2021-08-11 18:04 ` Pali Rohár
2021-08-12 9:28 ` Guillaume Nault
2021-08-12 13:48 ` Pali Rohár
2021-08-12 18:26 ` Guillaume Nault
2021-08-12 19:04 ` Pali Rohár
2021-08-16 16:11 ` Guillaume Nault
2021-08-16 16:23 ` Pali Rohár
2021-08-17 16:05 ` Guillaume Nault
2021-08-17 16:21 ` Pali Rohár
2022-07-09 12:09 ` Pali Rohár
2022-07-12 17:34 ` Guillaume Nault
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=20210810160450.eluiktsp7oentxo3@pali \
--to=pali@kernel.org \
--cc=davem@davemloft.net \
--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=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).