From: Jeff Layton <jlayton@kernel.org>
To: Luis Henriques <lhenriques@suse.com>,
"Yan, Zheng" <zyan@redhat.com>, Sage Weil <sage@redhat.com>,
Ilya Dryomov <idryomov@gmail.com>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ceph: initialize superblock s_time_gran to 1
Date: Thu, 27 Jun 2019 10:41:07 -0400 [thread overview]
Message-ID: <0459c2a46200194c14b7474f55071b12fbc3d594.camel@kernel.org> (raw)
In-Reply-To: <20190627135122.12817-1-lhenriques@suse.com>
On Thu, 2019-06-27 at 14:51 +0100, Luis Henriques wrote:
> Having granularity set to 1us results in having inode timestamps with a
> accurancy different from the fuse client (i.e. atime, ctime and mtime will
> always end with '000'). This patch normalizes this behaviour and sets the
> granularity to 1.
>
> Signed-off-by: Luis Henriques <lhenriques@suse.com>
> ---
> fs/ceph/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Hi!
>
> As far as I could see there are no other side-effects of changing
> s_time_gran but I'm really not sure why it was initially set to 1000 in
> the first place so I may be missing something.
>
> diff --git a/fs/ceph/super.c b/fs/ceph/super.c
> index d57fa60dcd43..35dd75bc9cd0 100644
> --- a/fs/ceph/super.c
> +++ b/fs/ceph/super.c
> @@ -980,7 +980,7 @@ static int ceph_set_super(struct super_block *s, void *data)
> s->s_d_op = &ceph_dentry_ops;
> s->s_export_op = &ceph_export_ops;
>
> - s->s_time_gran = 1000; /* 1000 ns == 1 us */
> + s->s_time_gran = 1;
>
> ret = set_anon_super(s, NULL); /* what is that second arg for? */
> if (ret != 0)
Looks like it was set that way since the client code was originally
merged. Was this an earlier limitation of ceph that is no longer
applicable?
In any case, I see no need at all to keep this at 1000, so:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2019-06-27 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:51 Luis Henriques
2019-06-27 14:41 ` Jeff Layton [this message]
2019-06-27 15:44 ` Sage Weil
2019-06-27 16:10 ` Jeff Layton
2019-06-28 9:30 ` Luis Henriques
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=0459c2a46200194c14b7474f55071b12fbc3d594.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=lhenriques@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@redhat.com \
--cc=zyan@redhat.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
all inboxes | Powered by JetHome®