From: "Éric Piel" <E.A.B.Piel@tudelft.nl>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH, resend] relatime: Let relatime update atime at least once per day
Date: Sun, 28 Dec 2008 20:04:50 +0100 [thread overview]
Message-ID: <4957CDD2.9040903@tudelft.nl> (raw)
In-Reply-To: <20081228152901.GB13565@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Matthew Garrett schreef:
> Ensure relatime updates atime at least once per day
>
> Allow atime to be updated once per day even with relatime. This lets
> utilities like tmpreaper (which delete files based on last access time)
> continue working.
:
Sorry, but I doubt it's a good idea. First, it breaks the simple
semantic of relatime (mtime > atime?), mixing it with a rather arbitrary
constant. Second, and most important, there are lots of workloads which
will be strongly affected by this modification. For instance, running
md5sum daily on the filesystem will cause a write for every file.
I think that to solve the problem for your use case, it's better to use
a different approach such as mounting separately /tmp (with the atime
option).
Eric
[-- Attachment #2: E_A_B_Piel.vcf --]
[-- Type: text/x-vcard, Size: 367 bytes --]
begin:vcard
fn;quoted-printable:=C3=89ric Piel
n;quoted-printable:Piel;=C3=89ric
org:Technical University of Delft;Software Engineering Research Group
adr:HB 08.080;;Mekelweg 4;Delft;;2628 CD;The Netherlands
email;internet:E.A.B.Piel@tudelft.nl
tel;work:+31 15 278 6338
tel;cell:+31 6 2437 9135
x-mozilla-html:FALSE
url:http://pieleric.free.fr
version:2.1
end:vcard
next prev parent reply other threads:[~2008-12-28 19:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 15:29 [PATCH, resend] relatime: Let relatime update atime at least once per day Matthew Garrett
2008-12-28 18:35 ` Jesper Juhl
2008-12-28 20:19 ` Matthew Garrett
2008-12-28 19:04 ` Éric Piel [this message]
2008-12-28 19:59 ` Matthew Garrett
2008-12-28 21:24 ` Éric Piel
2008-12-28 21:36 ` Matthew Wilcox
2008-12-28 21:38 ` Matthew Garrett
2009-01-08 12:29 ` Peter Moulder
2009-01-08 13:32 ` Matthew Garrett
[not found] <fa.v5U3CdNO/bF+SC9Lx2IrNK0ksBw@ifi.uio.no>
[not found] ` <fa./Q0ErjvWHKMrOCYUQaeuJBQ1U8A@ifi.uio.no>
[not found] ` <fa.pfgwZ2DZZy7psm2o5/f7mrtpRUA@ifi.uio.no>
[not found] ` <fa./KluIoJB1+QtfX+SyKcE+SysfKU@ifi.uio.no>
[not found] ` <fa.YKGFdZah7xr94yJzEWemIAnOKNA@ifi.uio.no>
2008-12-28 22:53 ` Sitsofe Wheeler
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=4957CDD2.9040903@tudelft.nl \
--to=e.a.b.piel@tudelft.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@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;
as well as URLs for NNTP newsgroup(s).