From: Stephen Hemminger <stephen@networkplumber.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, netdev@vger.kernel.org,
mcgrof@kernel.org, tytso@mit.edu
Subject: Re: RFC: Ioctl v2
Date: Sat, 21 May 2022 12:45:59 -0700 [thread overview]
Message-ID: <20220521124559.69414fec@hermes.local> (raw)
In-Reply-To: <20220521164546.h7huckdwvguvmmyy@moria.home.lan>
On Sat, 21 May 2022 12:45:46 -0400
Kent Overstreet <kent.overstreet@gmail.com> wrote:
> On Fri, May 20, 2022 at 10:31:02PM +0200, Andrew Lunn wrote:
> > > I want to circulate this and get some comments and feedback, and if
> > > no one raises any serious objections - I'd love to get collaborators
> > > to work on this with me. Flame away!
> >
> > Hi Kent
> >
> > I doubt you will get much interest from netdev. netdev already
> > considers ioctl as legacy, and mostly uses netlink and a message
> > passing structure, which is easy to extend in a backwards compatible
> > manor.
>
> The more I look at netlink the more I wonder what on earth it's targeted at or
> was trying to solve. It must exist for a reason, but I've written a few ioctls
> myself and I can't fathom a situation where I'd actually want any of the stuff
> netlink provides.
Netlink was built for networking operations, you want to set something like a route with a large
number of varying parameters in one transaction. And you don't want to have to invent
a new system call every time a new option is added.
Also, you want to monitor changes and see these events for a userspace control
application such as a routing daemon.
next prev parent reply other threads:[~2022-05-21 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 16:16 RFC: Ioctl v2 Kent Overstreet
2022-05-20 20:31 ` Andrew Lunn
2022-05-21 16:45 ` Kent Overstreet
2022-05-21 18:55 ` Andrew Lunn
2022-05-21 19:45 ` Stephen Hemminger [this message]
2022-05-25 17:02 ` Kent Overstreet
2022-05-25 20:57 ` Andrew Lunn
2022-06-01 8:29 ` Leon Romanovsky
2022-05-20 23:45 ` Theodore Ts'o
2022-05-25 17:20 ` Kent Overstreet
2022-06-09 22:02 ` Jan Engelhardt
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=20220521124559.69414fec@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.