From: Rob Landley <rob@landley.net>
To: Dominique Martinet <dominique.martinet@cea.fr>
Cc: v9fs-developer@lists.sourceforge.net, ericvh@gmail.com,
linux-fsdevel@vger.kernel.org
Subject: Re: [V9fs-developer] [RFC PATCH] First RFC version of a new cache=mmap model.
Date: Sat, 07 Sep 2013 04:57:22 -0500 [thread overview]
Message-ID: <1378547842.8385.2@driftwood> (raw)
In-Reply-To: <1378219078-30692-1-git-send-email-dominique.martinet@cea.fr> (from dominique.martinet@cea.fr on Tue Sep 3 09:37:58 2013)
On 09/03/2013 09:37:58 AM, Dominique Martinet wrote:
> - Add cache=mmap option
> - Try to keep most operations synchronous
>
> Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
> ---
>
> Hi,
>
> I brought up the issue of mmap being read-only with cache=none a bit
> ago, and worked on it since.
>
> Here's what this patch does:
> - Add an option cache=mmap (or just mmap, like other caches), nothing
> changes for default or other caches.
Interesting.
Should this become the default behavior instead of "none" for
non-readonly mounts? (What's the point of the "none" mode now that we
have writeable mmap implemented, is there any advantage?)
Rob
next prev parent reply other threads:[~2013-09-07 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378217781-27942-1-git-send-email-dominique.martinet@cea.fr>
2013-09-03 14:37 ` [RFC PATCH] First RFC version of a new cache=mmap model Dominique Martinet
2013-09-07 9:57 ` Rob Landley [this message]
2013-09-07 14:46 ` [V9fs-developer] " Dominique Martinet
2013-09-17 11:51 ` [RFC PATCH V2] " Dominique Martinet
2013-10-21 11:06 ` [PATCH] 9P: introduction " Dominique Martinet
[not found] ` <CAFkjPTnU6r+BD84-TkLGV18vsPvTF7+x3KNhN4ZHor-qx698fg@mail.gmail.com>
2013-09-03 14:44 ` [RFC PATCH] First RFC version " MARTINET Dominique
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=1378547842.8385.2@driftwood \
--to=rob@landley.net \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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.