All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: <dedekind1@gmail.com>
Cc: richard@nod.at, linux-mtd@lists.infradead.org, adrian.hunter@intel.com
Subject: Re: [PATCH] ubifs: Introduce a mount option of force_atime.
Date: Mon, 8 Jun 2015 17:55:11 +0800	[thread overview]
Message-ID: <5575667F.5020604@cn.fujitsu.com> (raw)
In-Reply-To: <1433755985.28854.3.camel@sauron.fi.intel.com>

On 06/08/2015 05:33 PM, Artem Bityutskiy wrote:
> On Mon, 2015-06-08 at 16:27 +0800, Dongsheng Yang wrote:
>> Currently, ubifs does not support access time anyway. I understand
>> that there is a overhead to update inode in each access from user.
>>
>> But for the following two reasons, I think we can make it optional
>> to user.
>>
>> (1). More and more flash storage in server are trying to use ubifs,
>> it is not only for a device such as mobile phone any more, we want
>> to use it in more and more generic way. Then we need to compete
>> with some other main filesystems. From this point, access time is
>> necessary to us, at least as a choice to user currently.
>
> Hi,
>
> Could you please re-send this patch with the following list in CC:
>
> linux-fsdevel@vger.kernel.org

Okey, thanx
>
> This patch will probably need VFS-scope discussion, this is why I am
> asking to CC the general linux file-systems development mailing list.
>

> Thanks!
>
> .
>

      reply	other threads:[~2015-06-08 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08  8:27 [PATCH] ubifs: Introduce a mount option of force_atime Dongsheng Yang
2015-06-08  8:44 ` Richard Weinberger
2015-06-08  9:11   ` Dongsheng Yang
2015-06-08  9:33     ` Richard Weinberger
2015-06-08  9:54       ` Dongsheng Yang
2015-06-08 10:02         ` Richard Weinberger
2015-06-08 10:03           ` Dongsheng Yang
2015-06-08  9:33 ` Artem Bityutskiy
2015-06-08  9:55   ` Dongsheng Yang [this message]

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=5575667F.5020604@cn.fujitsu.com \
    --to=yangds.fnst@cn.fujitsu.com \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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.