linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>, dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v6] ubifs: introduce UBIFS_ATIME_SUPPORT to ubifs
Date: Sat, 3 Oct 2015 20:34:45 +0200	[thread overview]
Message-ID: <56101FC5.6090900@nod.at> (raw)
In-Reply-To: <1440126626-18446-1-git-send-email-yangds.fnst@cn.fujitsu.com>

Am 21.08.2015 um 05:10 schrieb Dongsheng Yang:
> To make ubifs support atime flexily, this commit introduces
> a Kconfig option named as UBIFS_ATIME_SUPPORT.
> 
> With UBIFS_ATIME_SUPPORT=n:
> 	ubifs keeps the full compatibility to no_atime from
> the start of ubifs.
> =================UBIFS_ATIME_SUPPORT=n=======================
> -o - no atime
> -o atime - no atime
> -o noatime - no atime
> -o relatime - no atime
> -o strictatime - no atime
> -o lazyatime - no atime
> 
> With UBIFS_ATIME_SUPPORT=y:
> 	ubifs supports the atime same with other main stream
> file systems.
> =================UBIFS_ATIME_SUPPORT=y=======================
> -o - default behavior (relatime currently)
> -o atime - atime support
> -o noatime - no atime support
> -o relatime - relative atime support
> -o strictatime - strict atime support
> -o lazyatime - lazy atime support
> 
> Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
> ---
> 	-v2:
> 		implement update_time for ubifs
> 	-v3:
> 		Oops, forgot to assign update_time for
> 		ubifs_dir_inode_operations.
> 	-v4:
> 		drop the patch to change 'Y' to 'N' in
> 		Kconfig
> 	-v5:
> 		simplify the warning in atime supporting
> 	-v6:
> 		* replace ubifs_warn with ubifs_msg
> 		* rewrite the messages in Kconfig as Artem suggested
> 		* remove S_VERSION related code
>  fs/ubifs/Kconfig | 15 +++++++++++++++
>  fs/ubifs/dir.c   |  3 +++
>  fs/ubifs/file.c  | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
>  fs/ubifs/super.c | 12 ++++++++++--
>  fs/ubifs/ubifs.h |  1 +
>  5 files changed, 77 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/ubifs/Kconfig b/fs/ubifs/Kconfig
> index ba66d50..7ff7712 100644
> --- a/fs/ubifs/Kconfig
> +++ b/fs/ubifs/Kconfig
> @@ -35,3 +35,18 @@ config UBIFS_FS_ZLIB
>  	default y
>  	help
>  	  Zlib compresses better than LZO but it is slower. Say 'Y' if unsure.
> +
> +config UBIFS_ATIME_SUPPORT
> +	bool "Access time support" if UBIFS_FS
> +	depends on UBIFS_FS
> +	default n
> +	help
> +	  Originally UBIFS did not support atime, because it looked like a bad idea due
> +	  increased flash wear. This option adds atime support and it is disabled by default
> +	  to preserve the old behavior. If you enable this option, UBIFS starts updating atime,
> +	  which means that file-system read operations will cause writes (inode atime
> +	  updates). This may affect file-system performance and increase flash device wear,
> +	  so be careful. How often atime is updated depends on the selected strategy:
> +	  strictatime is the "heavy", relatime is "lighter", etc.
> +
> +	  If unsure, say 'N'
> diff --git a/fs/ubifs/dir.c b/fs/ubifs/dir.c
> index 27060fc..8d93427 100644
> --- a/fs/ubifs/dir.c
> +++ b/fs/ubifs/dir.c
> @@ -1187,6 +1187,9 @@ const struct inode_operations ubifs_dir_inode_operations = {
>  	.getxattr    = ubifs_getxattr,
>  	.listxattr   = ubifs_listxattr,
>  	.removexattr = ubifs_removexattr,
> +#ifdef CONFIG_UBIFS_ATIME_SUPPORT
> +	.update_time = ubifs_update_time,
> +#endif
>  };
>  
>  const struct file_operations ubifs_dir_operations = {
> diff --git a/fs/ubifs/file.c b/fs/ubifs/file.c
> index 35efc10..423ce6b 100644
> --- a/fs/ubifs/file.c
> +++ b/fs/ubifs/file.c
> @@ -1364,6 +1364,45 @@ static inline int mctime_update_needed(const struct inode *inode,
>  }
>  
>  /**
> + * ubifs_update_time - update time of inode.
> + * @inode: inode to update
> + *
> + * This function updates time of the inode.
> + */
> +int ubifs_update_time(struct inode *inode, struct timespec *time,
> +			     int flags)

This function should be under an "#ifdef CONFIG_UBIFS_ATIME_SUPPORT".

Beside of that,
Reviewed-by: Richard Weinberger <richard@nod.at>

I think we can queue it for v4.4. Artem, what do you think?

Thanks,
//richard

  reply	other threads:[~2015-10-03 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  3:10 [PATCH v6] ubifs: introduce UBIFS_ATIME_SUPPORT to ubifs Dongsheng Yang
2015-10-03 18:34 ` Richard Weinberger [this message]
2015-11-06  9:25   ` Richard Weinberger
2015-11-07  4:35     ` Dongsheng Yang

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=56101FC5.6090900@nod.at \
    --to=richard@nod.at \
    --cc=dedekind1@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=yangds.fnst@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).