All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Beattie <beattie@beattie-home.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ioctl's suck?
Date: Sun, 03 Aug 2008 10:04:55 -0700	[thread overview]
Message-ID: <1217783095.6280.63.camel@kokopelli> (raw)
In-Reply-To: <20080803135622.7f624327@lxorguk.ukuu.org.uk>

On Sun, 2008-08-03 at 13:56 +0100, Alan Cox wrote:
> > I could add a control device and pass ascii strings for status and OOB
> > messages, would that be an improvement?
> 
> Usually not. The idea that ioctl can be replaced with ascii messages is
> clueless rubbish that generally gets spouted by people with their head
> in the clouds of conceptual elegance and no grasp of reality.

Yeah, I can see that.  Though the case has been made that ioctls are
only usable by C/C++ while I'm sure there are other languages, I'm
working in the embedded space and mostly work with C and sh so my
experience is limited and that is of less direct importance to me.

> 
> There are certain things you can expose that way usefully via sysfs
> - things like general stateless status information. Ioctl however provides
> an interface tied to file handle not name (which is essential in a hotplug
> environment) and an ordering to events so you know the response you get
> matches the query you made.

Yeah coherence (if I'm using that word correctly) would be critical, and
a separate file handle would make that tricky.


> Alan
-- 
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


  reply	other threads:[~2008-08-03 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 21:54 ioctl's suck? Brian Beattie
2008-08-03  1:18 ` Mikael Pettersson
2008-08-03 12:56 ` Alan Cox
2008-08-03 17:04   ` Brian Beattie [this message]
     [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=1217783095.6280.63.camel@kokopelli \
    --to=beattie@beattie-home.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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.