From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Mapping a piece of one process' addrspace to another?
Date: 07 Mar 2001 17:22:31 -0600 [thread overview]
Message-ID: <m3u255411k.fsf@austin.jhcloos.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0103070402160.2127-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0103070402160.2127-100000@weyl.math.psu.edu> (Alexander Viro's message of "Wed, 7 Mar 2001 04:09:31 -0500 (EST)")
>>>>> "AV" == Alexander Viro <viro@math.psu.edu> writes:
AV> Double ugh. Why bother with ioctl() when you can just have a
AV> second channel and do read()/write() on it?
Because you cannot rewrite -- or even re-compile -- every app this
should support. OSS emulation by ALSA is a great example, given
how many binary-only apps already exist which need OSS emulation
on an ALSA box.
I'm sure sound is not the only real application for this.
-JimC
--
James H. Cloos, Jr. <http://jhcloos.com/public_key> 1024D/ED7DAEA6
<cloos@jhcloos.com> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6
next prev parent reply other threads:[~2001-03-07 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 5:19 Mapping a piece of one process' addrspace to another? Jeremy Elson
2001-03-07 5:55 ` Alexander Viro
2001-03-07 6:02 ` Marcelo Tosatti
2001-03-07 8:13 ` Jeremy Elson
2001-03-07 8:40 ` Alexander Viro
2001-03-07 8:54 ` Jeremy Elson
2001-03-07 9:09 ` Alexander Viro
2001-03-07 23:22 ` James H. Cloos Jr. [this message]
2001-03-07 9:04 ` Abramo Bagnara
2001-03-07 9:10 ` Alexander Viro
2001-03-07 9:20 ` Abramo Bagnara
2001-03-07 9:49 ` Alexander Viro
2001-03-07 13:01 ` Abramo Bagnara
2001-03-07 21:02 ` Jeremy Elson
2001-03-07 8:58 ` Abramo Bagnara
2001-03-07 18:17 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2001-03-07 10:51 Manfred Spraul
2001-03-07 13:57 Jesse Pollard
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=m3u255411k.fsf@austin.jhcloos.com \
--to=cloos@jhcloos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox