From: Tejun Heo <tj@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: mszeredi@suse.cz, linux-kernel@vger.kernel.org,
fuse-devel@lists.sourceforge.net, polynomial-c@gentoo.org,
akpm@linux-foundation.org
Subject: Re: [fuse-devel] [PATCH] FUSE/CUSE: implement direct mmap support
Date: Thu, 11 Feb 2010 08:43:32 +0900 [thread overview]
Message-ID: <4B7344A4.1030607@kernel.org> (raw)
In-Reply-To: <E1NfE50-0001EK-Ao@pomaz-ex.szeredi.hu>
Hello,
On 02/11/2010 12:02 AM, Miklos Szeredi wrote:
>> Yeah, sure. FUSE server is free to give them separate regions. The
>> only restriction is the SHMLBA alignment which is pretty easy to
>> adhere to.
>
> What I really meant was: does it ever happen that mapping a *single
> open file* of a chardev twice will result in two different maps?
> Or will the maps be only different if it was a different open of the
> device?
I don't know if there is one but ->mmap() implementation is definitely
allowed to do that.
> If there's a pattern there, we might make the sharing/non-sharing
> automated, and greatly simplify the interface.
Isn't the interface pretty simple as it is? If we want to make it
easier for API users by imposing limits, I think the correct layer to
do that would be at the library level.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-02-10 23:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 6:08 [PATCH] FUSE/CUSE: implement direct mmap support Tejun Heo
2010-02-09 14:59 ` [fuse-devel] " Miklos Szeredi
2010-02-10 11:22 ` Tejun Heo
2010-02-10 11:29 ` Miklos Szeredi
2010-02-10 11:56 ` Tejun Heo
2010-02-10 12:15 ` Miklos Szeredi
2010-02-10 12:35 ` Tejun Heo
2010-02-10 15:02 ` Miklos Szeredi
2010-02-10 23:43 ` Tejun Heo [this message]
2010-02-11 9:31 ` Miklos Szeredi
2010-02-11 9:51 ` Miklos Szeredi
2010-02-11 11:54 ` Tejun Heo
2010-02-11 12:25 ` Miklos Szeredi
2010-02-11 12:49 ` Tejun Heo
2010-02-11 12:46 ` Miklos Szeredi
2010-02-11 13:05 ` Tejun Heo
2010-02-11 13:08 ` Miklos Szeredi
2010-02-11 13:40 ` Tejun Heo
2010-02-11 11:47 ` Tejun Heo
2010-02-11 12:34 ` Miklos Szeredi
2010-02-11 12:56 ` Tejun Heo
2010-02-11 13:01 ` Miklos Szeredi
2010-02-11 13:30 ` Tejun Heo
2010-02-11 13:40 ` Miklos Szeredi
2010-02-11 13:58 ` Tejun Heo
2010-02-11 14:40 ` Miklos Szeredi
2010-02-12 0:07 ` Tejun Heo
2010-02-12 0:25 ` Tejun Heo
2010-02-12 9:55 ` Miklos Szeredi
2010-02-12 13:33 ` Tejun Heo
2010-02-12 13:53 ` Miklos Szeredi
2010-02-12 17:56 ` Tejun Heo
2010-02-10 11:36 ` Tejun Heo
2010-02-10 8:24 ` Goswin von Brederlow
2010-02-10 8:40 ` Miklos Szeredi
2010-02-10 8:58 ` Paul Schutte
2010-02-10 10:02 ` Paul Schutte
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=4B7344A4.1030607@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=polynomial-c@gentoo.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.