From: Andreas Dilger <adilger@clusterfs.com>
To: Steve French <smfrench@austin.rr.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
samba-technical@lists.samba.org
Subject: Re: ctime set by truncate even if NOCMTIME requested
Date: Tue, 20 Sep 2005 06:11:57 -0600 [thread overview]
Message-ID: <20050920121157.GG12946@schatzie.adilger.int> (raw)
In-Reply-To: <432F70EF.9010100@austin.rr.com>
On Sep 19, 2005 21:16 -0500, Steve French wrote:
> It does seem like
> utime(filename, timeval)
> may be the only time we want to send time changes to the server but I am
> not certain how risky such an approach is even after scanning fs/open.c
> to ignore time changes except when both ATIME/MTIME/CTIME are set at the
> same time (as they are in sys_utime and do_utimes). Most people
> probably don't care if the server and client clocks are not too far off,
> but it does affect performance (presumably even noticeable on something
> like fsx test)
For Lustre (since we are patching the VFS anyways) we have added an
ATTR_CTIME_SET flag to distinguish whether the client has explicitly
set the ia_ctime field, or if it is an implicit update.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2005-09-20 12:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 17:51 Steve French
2005-09-19 18:58 ` Trond Myklebust
2005-09-19 20:58 ` Steve French
2005-09-19 21:28 ` Trond Myklebust
[not found] ` <432F5968.1020106@austin.rr.com>
2005-09-20 1:36 ` Trond Myklebust
2005-09-20 2:16 ` Steve French
2005-09-20 12:11 ` Andreas Dilger [this message]
2005-09-20 8:52 ` Miklos Szeredi
2005-09-20 10:05 ` Miklos Szeredi
2005-09-20 12:12 ` Trond Myklebust
2005-09-20 12:20 ` Miklos Szeredi
2005-09-20 12:27 ` Trond Myklebust
2005-09-20 8:48 ` Miklos Szeredi
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=20050920121157.GG12946@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@austin.rr.com \
--cc=trond.myklebust@fys.uio.no \
/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®