From: Tejun Heo <tj@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] OSS Proxy using CUSE
Date: Fri, 29 Aug 2008 12:47:10 +0200 [thread overview]
Message-ID: <48B7D3AE.3050108@kernel.org> (raw)
In-Reply-To: <s5htzd4gl3n.wl%tiwai@suse.de>
Hello,
Takashi Iwai wrote:
> Thanks for info. Just a quick glance, CUSE looks like a good
> abstraction for this kind of things.
>
> I've been thinking that the tunneling to an OSS-emulation daemon would
> be the best way, too, and I actually made a similar hack (not based on
> FUSE but own kernel module).
>
> It was presented in SUSE Labs conference a few years ago. And the
> reaction by audience at that time was what Adrian showed -- why do we
> need such a complexity at all? Well, as long as we have OSS API and
> its applications, we should keep supporting them in a good form.
>
> Anyway, my implementation at that time was too hackish and I gave up
> soon. If it can be implemented in a generic framework like CUSE,
> it's a good chance to merge to the upstream.
>
> One thing I couldn't find in your code is the mmap support.
> The mmap support is crucial for some apps, typically used for games.
> Am I missing something?
mmap is essential for some apps? Aiee... I was hoping to skip that one
after reading strong discouragement against it in the OSS programming
manual from 4front.
Adding it shouldn't be too difficult. I'll give it a shot after other
stuff settles down.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-29 10:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:05 [ANNOUNCE] OSS Proxy using CUSE Tejun Heo
2008-08-28 20:01 ` Adrian Bunk
2008-08-28 22:18 ` Greg KH
2008-08-28 23:05 ` H. Peter Anvin
2008-08-28 23:14 ` Greg KH
2008-08-28 23:38 ` H. Peter Anvin
2008-08-28 23:32 ` Alan Cox
2008-08-29 1:33 ` Tejun Heo
2008-08-29 6:50 ` Adrian Bunk
2008-08-29 7:26 ` Tejun Heo
2008-08-29 8:09 ` Miklos Szeredi
2008-08-29 8:21 ` Adrian Bunk
2008-08-29 8:28 ` Tejun Heo
2008-09-02 15:25 ` Pavel Machek
2008-11-27 20:59 ` Jan Engelhardt
2008-11-28 2:23 ` Tejun Heo
2008-11-28 11:35 ` Jan Engelhardt
2008-11-28 12:02 ` Tejun Heo
2008-11-28 12:56 ` Jan Engelhardt
2008-08-29 10:40 ` Takashi Iwai
2008-08-29 10:47 ` Tejun Heo [this message]
2009-04-14 2:46 ` [ANNOUNCE] OSS Proxy 1.2 " Tejun Heo
2009-04-22 19:58 ` Miklos Szeredi
2009-04-22 23:59 ` Tejun Heo
2009-06-20 6:13 ` Tejun Heo
2009-06-20 6:37 ` Tejun Heo
2009-04-28 16:01 ` Miklos Szeredi
2009-04-28 16:42 ` Takashi Iwai
2009-04-28 17:17 ` Miklos Szeredi
2009-04-28 19:32 ` Takashi Iwai
2009-04-28 20:12 ` Miklos Szeredi
2009-04-28 21:34 ` Takashi Iwai
2009-04-29 7:13 ` Miklos Szeredi
2009-04-28 23:35 ` Tejun Heo
2009-04-29 7:20 ` Miklos Szeredi
2009-04-29 7:46 ` Tejun Heo
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=48B7D3AE.3050108@kernel.org \
--to=tj@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tiwai@suse.de \
/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