public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Mikael Bouillot <hmajxxlh@corbac.com>
Cc: Miklos Szeredi <mszeredi@suse.cz>,
	lkml <linux-kernel@vger.kernel.org>,
	fuse-devel@lists.sourceforge.net
Subject: Re: OSS Proxy Jack slave
Date: Sat, 05 Jun 2010 11:05:45 +0200	[thread overview]
Message-ID: <4C0A1369.9010601@kernel.org> (raw)
In-Reply-To: <20100605085045.GA5630@alia.nute.net>

Hello,

(cc'ing Miklos and mailing lists)

On 06/05/2010 10:50 AM, Mikael Bouillot wrote:
> Just a quick question: have you reached some form of understanding
> with Miklos Szeredi over the direct mmap in FUSE issue?
> 
> I've read the thread from February 2010, and though most of the
> kernel material fly way over my head, I've got the general idea.
> 
> FUSD has had mmap support since around the time I started using
> oss2jack, so I don't know exactly how many apps I use require it
> (besides Quake3). I'll put a printf in my oss2jack's mmap() to
> see what I'll be missing.
> 
> I could use a patched FUSE, but stopping to have to maintain a
> piece of out-of-tree kernel code was The. Whole. Point. of
> switching from FUSD to a CUSE-based system T_T

Miklos, any update on the mmap interface?

Thanks.

-- 
tejun

       reply	other threads:[~2010-06-05  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100601092456.GA23572@alia.nute.net>
     [not found] ` <4C066CF4.2050902@gmail.com>
     [not found]   ` <20100605085045.GA5630@alia.nute.net>
2010-06-05  9:05     ` Tejun Heo [this message]
2010-06-09 10:08       ` [fuse-devel] OSS Proxy Jack slave Miklos Szeredi
2010-06-10 11:23         ` Tejun Heo
2010-06-10 11:52           ` Miklos Szeredi
2010-06-10 13:13             ` Tejun Heo
2010-06-10 13:28               ` Miklos Szeredi
2010-06-10 15:26                 ` 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=4C0A1369.9010601@kernel.org \
    --to=tj@kernel.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=hmajxxlh@corbac.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@suse.cz \
    /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