All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Al Hooton <al@hootons.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: ioctl assignment strategy?
Date: Fri, 17 Dec 2004 15:48:54 -0800	[thread overview]
Message-ID: <20041217234854.GA24506@kroah.com> (raw)
In-Reply-To: <41C04FFA.6010407@nortelnetworks.com>

On Wed, Dec 15, 2004 at 08:53:46AM -0600, Chris Friesen wrote:
> Greg KH wrote:
> 
> >Minor one coming, why do you want to use an ioctl?  ioctls are generally
> >frowned upon these days, and trying to add a new one is a tough and
> >arduous process, that is not for the weak, or faint of heart.
> 
> Just curious--what other options would you suggest for arbitrary char 
> devices to allow for control that doesn't fit nicely into the read/write 
> paradigm?

Rethink the way you want to control your device.  Seriously, a lot of
ioctls can be broken down into single device files, single sysfs files,
or other such things (a whole new fs as a last resort too.)

So, what does your ioctls do?

thanks,

greg k-h

  reply	other threads:[~2004-12-17 23:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 23:31 ioctl assignment strategy? Al Hooton
2004-12-15  0:46 ` Greg KH
2004-12-15 14:53   ` Chris Friesen
2004-12-17 23:48     ` Greg KH [this message]
2004-12-20 17:37       ` Chris Friesen
2004-12-20 22:48         ` Pjotr Kourzanov
2004-12-21  0:32           ` Alan Cox
2004-12-21  2:06             ` Lee Revell
2004-12-21 12:51             ` Olivier Galibert
2004-12-21 17:24         ` Greg KH
2004-12-22 17:16   ` Al Hooton

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=20041217234854.GA24506@kroah.com \
    --to=greg@kroah.com \
    --cc=al@hootons.org \
    --cc=cfriesen@nortelnetworks.com \
    --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.