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: Wed, 10 Feb 2010 21:35:14 +0900 [thread overview]
Message-ID: <4B72A802.6040009@kernel.org> (raw)
In-Reply-To: <E1NfBTc-0000vk-59@pomaz-ex.szeredi.hu>
Hello, Miklos.
On 02/10/2010 09:15 PM, Miklos Szeredi wrote:
>> Same offset -> same page doesn't hold.
>
> Right, I really meant same page -> same offset. If the same offset is
> mapped to multiple pages: no problem. If the same page is mapped to
> multiple offsets, then obviously it's not going to work properly.
Yeap.
>> Can you please elaborate how you think the thing can work without
>> referencing the proposed implementation? Let's find out where the
>> misundertanding is.
>
> Thinking about it I'm not really sure...
>
> Maybe the problem is that the propsed solution allows too much
> freedom. Normally there's a 1:1 relationship between pages and
> offsets. But we want to break that for CUSE, because two different
> mappings of a char dev might point to completely different pages,
> right?
Yeap. It basically behaves like each mmap() instance is a shm
instance and the offset into dmmap_regions is the shmkey.
> When does that happen? Can it happen that two mappings of the same
> file descriptor will have different backing pages?
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.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-02-10 12:28 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 [this message]
2010-02-10 15:02 ` Miklos Szeredi
2010-02-10 23:43 ` Tejun Heo
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=4B72A802.6040009@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox