Re: ctime set by truncate even if NOCMTIME requested

[Andreas Dilger]

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/