From: Valdis.Kletnieks@vt.edu
To: Andreas Dilger <adilger@dilger.ca>
Cc: yangsheng <sickamd@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, swhiteho@redhat.com,
sickadm@gmail.com
Subject: Re: [PATCH resend] Update atime from future.
Date: Tue, 04 Jan 2011 15:31:53 -0500 [thread overview]
Message-ID: <32922.1294173113@localhost> (raw)
In-Reply-To: Your message of "Tue, 04 Jan 2011 12:13:37 MST." <2321F6F6-1042-48E8-9F21-12C52E8FFFCC@dilger.ca>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Tue, 04 Jan 2011 12:13:37 MST, Andreas Dilger said:
> On 2011-01-04, at 11:21, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 04 Jan 2011 16:56:58 +0800, yangsheng said:
> >> If atime has been wrong set to future, then it cannot
> >> be updated back to current time.
> >>
> >> +#define RELATIME_MARGIN (24 * 60 * 60)
> >
> > Nice patch overall. Should this be a #define, or a CONFIG_ variable,
> > or a tweakable /proc/sys/fs variable? Or am I senile and we thrashed
> > all this out once before when the relatime code landed?
>
> I recall the consensus was that a /proc tunable was "too much" for the
> initial patch.
OK, in that case yangsheng's patch is probably good to go.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2011-01-04 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 8:56 [PATCH resend] Update atime from future yangsheng
2011-01-04 9:02 ` Andreas Schwab
2011-01-04 9:05 ` YangSheng
2011-01-04 18:21 ` Valdis.Kletnieks
2011-01-04 19:13 ` Andreas Dilger
2011-01-04 20:31 ` Valdis.Kletnieks [this message]
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=32922.1294173113@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sickadm@gmail.com \
--cc=sickamd@gmail.com \
--cc=swhiteho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.