From: majianpeng <majianpeng@gmail.com>
To: "Yan, Zheng" <ukernel@gmail.com>
Cc: sage <sage@inktank.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Re: [PATCH] ceph:Update the file time after mmap-write.
Date: Fri, 12 Jul 2013 10:26:26 +0800 [thread overview]
Message-ID: <201307121026243710713@gmail.com> (raw)
In-Reply-To: CAAM7YAmAwNEX4x2sbTocZTtP01GwW62UD5m9JDWBsRUuf7i1gQ@mail.gmail.com
>On Thu, Jul 11, 2013 at 3:53 PM, majianpeng <majianpeng@gmail.com> wrote:
>>>On Thu, Jul 11, 2013 at 9:17 AM, majianpeng <majianpeng@gmail.com> wrote:
>>>> Although, mmap-write of ceph update the time of file using
>>>> file_update_time.Because it don't mark the relative cap so the time
>>>> can't save.
>>>
>>>I think cephfs' mmap IO support is still broken. mmap IO does not respect
>>>ceph capabilities at all. It's possible that the kclient has no Fw cap when
>>>ceph_page_mkwrite is called.
>>>
>>>Yan, Zheng
>>>
>>>
>> Hi Yan,
>> For the read of mmap, i think we also add cap-check.
>> And i think we can rewrite the filemap_fault ect ceph_filemap_fault.
>> In ceph_filemap_fault, most code from filemap_fault, we only add cap-check for read-operation.
>> How about this or can you suggest anthor method?
>>
>
>This doesn't work. if a file is opened by multiple clients, the MDS
>doesn't issue Fcb caps to the client.
>If we add cap check to filemap_fault and page_mkwrite, they can block
>forever. To make mmap IO work
>properly, I think the only solution is introducing a new cache
>coherence protocol for mmap IO
>
Thanks your suggestion.
Unless we get the Fcb cap, we can do the mmap-io.How about this?
Because the cap can change,so we can using Fx to lock the file, so cap can't change.
>
>> Thanks!
>> Jianpeng Ma
next prev parent reply other threads:[~2013-07-12 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 1:17 [PATCH] ceph:Update the file time after mmap-write majianpeng
2013-07-11 1:42 ` Yan, Zheng
2013-07-11 1:49 ` majianpeng
2013-07-11 7:53 ` majianpeng
2013-07-11 9:03 ` Yan, Zheng
2013-07-12 2:26 ` majianpeng [this message]
2013-07-12 2:46 ` Gregory Farnum
2013-07-12 3:16 ` Yan, Zheng
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=201307121026243710713@gmail.com \
--to=majianpeng@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=ukernel@gmail.com \
/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.