From: Kent Overstreet <kent.overstreet@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: 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:46 -0400 [thread overview]
Message-ID: <20220521164546.h7huckdwvguvmmyy@moria.home.lan> (raw)
In-Reply-To: <Yof6hsC1hLiYITdh@lunn.ch>
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.
Why bother with getting a special socket type? Why asynchronous messages with
all the marshalling/unmarshalling that entails?
From what I've seen all we really want is driver private syscalls, and the
things about ioctls that suck are where it's _not_ like syscalls. Let's just
make it work more like normal function calls.
next prev parent reply other threads:[~2022-05-21 16: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 [this message]
2022-05-21 18:55 ` Andrew Lunn
2022-05-21 19:45 ` Stephen Hemminger
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=20220521164546.h7huckdwvguvmmyy@moria.home.lan \
--to=kent.overstreet@gmail.com \
--cc=andrew@lunn.ch \
--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 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).