[Top] [All Lists]

Re: [PATCH] enable possibility of ALL different atime mount options

To: SGI Project XFS mailing list <xfs@xxxxxxxxxxx>
Subject: Re: [PATCH] enable possibility of ALL different atime mount options
From: Roland Eggner <edvx1@xxxxxxxxxxxxxxxxxx>
Date: Fri, 30 Jan 2009 10:50:00 +0100
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>
In-reply-to: <49828666.7040809@xxxxxxxxxxx>
References: <200901300322.02079.edvx1@xxxxxxxxxxxxxxxxxx> <4982854D.8000808@xxxxxxxxxxx> <49828666.7040809@xxxxxxxxxxx>
Reply-to: "Roland Eggner" <edvx1@xxxxxxxxxxxxxxxxxx>
User-agent: KMail/1.9.6
On Friday Jan 30th 2009 at 05:47:34 Eric Sandeen wrote:
> Eric Sandeen wrote:
> > Roland Eggner wrote:
> >> Utako Kusaka has provided this patch
> >> http://oss.sgi.com/archives/xfs/2007-10/msg00168.html
> >> It works for me GRACEFULLY with ALL different atime mount options: 
> >> atime|noatime|relatime.
> >> Note, the mount options are effective, not only accepted.
> >> Prior to this patch, mount option atime has been ignored.
> > 
> > 
> > 
> >> Please put the patch to mainline, it would save worries for users, who 
> >> need the traditional atime
> >> bahavior.  Think of some corner cases for desktop usage.
> >>
> > 
> > Which specific problem is this fixing for you?
> > 
> > you say that atime is ignored; but:
> Sorry, I probably replied too quickly.  But I am still curious to know
> what problem you are seeing that this patch fixes.
> Thanks,
> -Eric

On Wed Oct 17th 2007 at 13:56:00 +0900 Utako Kusaka wrote:
>The atime is changed for reading but it returns to a previous value
>after unmount.
And his patch fixes this, nothing more and nothing less.
Think of desktop machines, where you sometimes need precise atime stamps,
and where atime only inode updates don't hurt performance because CPUs are
almost always idle.  Think of e.g. important cron jobs, you want to know
exactly, if at all, when and in which sequence they were executed.

Roland Eggner

<Prev in Thread] Current Thread [Next in Thread>