From: Tim Hockin <thockin@hockin.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Bernd Petrovitsch <bernd@firmix.at>,
Oliver Neukum <oliver@neukum.org>,
Steve French <smfltc@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: upcalls from kernel code to user space daemons
Date: Mon, 14 Jun 2004 15:54:38 -0700 [thread overview]
Message-ID: <20040614225438.GA22161@hockin.org> (raw)
In-Reply-To: <40CE2538.4060603@nortelnetworks.com>
On Mon, Jun 14, 2004 at 06:22:48PM -0400, Chris Friesen wrote:
> > > Not quite. The userspace is passing data down as well. I don't know
> >how you'd
> > > do that with read().
> >
> >For this you use write().
> Although I have to admit it's not pretty, and the performance improvements
> may not be worth the obfuscation of the code.
You know, I've never understood why people hate ioctl. Sometimes, it
really is what you want. Why impose structured data onto a 2-way
unstructred system (read/write) when you have a structured system at hand
(ioctl).
I like ioctl() when it makes sense. read() and write() are for data.
ioctl is for (tada!) control.
next prev parent reply other threads:[~2004-06-14 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:07 upcalls from kernel code to user space daemons Steve French
2004-06-14 18:30 ` Chris Friesen
2004-06-14 21:40 ` Oliver Neukum
2004-06-14 21:57 ` Chris Friesen
2004-06-14 22:08 ` Bernd Petrovitsch
2004-06-14 22:22 ` Chris Friesen
2004-06-14 22:54 ` Tim Hockin [this message]
2004-06-14 23:10 ` Randy.Dunlap
2004-06-14 22:54 ` Steve French
2004-06-15 9:06 ` Oliver Neukum
2004-06-18 23:08 ` H. Peter Anvin
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=20040614225438.GA22161@hockin.org \
--to=thockin@hockin.org \
--cc=bernd@firmix.at \
--cc=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=smfltc@us.ibm.com \
/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.