From: Brian Beattie <beattie@beattie-home.net>
To: linux-kernel@vger.kernel.org
Subject: ioctl's suck?
Date: Sat, 02 Aug 2008 14:54:56 -0700 [thread overview]
Message-ID: <1217714096.6280.35.camel@kokopelli> (raw)
The other day Linus (I think) made the statement, that I don't disagree
with, that I will parapharse as "ioctl's suck". If I recall correctly
and understand he was saying that a device that uses ioctls is broken.
(this is my paraphrase and if it offends anybody it is my fault not the
original author's).
This got me to thinking about a device driver that I'm working on.
Currently I have some ioctls to handle status and out of band messages
and I'm wondering about eliminating the ioctls. I'm wondering if
anybody has any ideas or opinions that they would like to share, about
just what i wrong with ioctls and/or how to avoid them.
I can see a number of problems with ioctls that I can'tr quite put into
words.
I could add a control device and pass ascii strings for status and OOB
messages, would that be an improvement?
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
Brian Beattie LFS12947 | "Honor isn't about making the right choices.
beattie@beattie-home.net | It's about dealing with the consequences."
www.beattie-home.net | -- Midori Koto
next reply other threads:[~2008-08-02 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 21:54 Brian Beattie [this message]
2008-08-03 1:18 ` Mikael Pettersson
2008-08-03 12:56 ` Alan Cox
2008-08-03 17:04 ` Brian Beattie
[not found] <fa.pDV0CxkUWw00OFrnybFqbUSeaQA@ifi.uio.no>
2008-08-03 1:36 ` Robert Hancock
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=1217714096.6280.35.camel@kokopelli \
--to=beattie@beattie-home.net \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome