From: Matthew Wilcox <matthew@wil.cx>
To: ?ric Piel <E.A.B.Piel@tudelft.nl>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
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 14:36:36 -0700 [thread overview]
Message-ID: <20081228213636.GB2002@parisc-linux.org> (raw)
In-Reply-To: <4957EEA7.3050101@tudelft.nl>
On Sun, Dec 28, 2008 at 10:24:55PM +0100, ?ric Piel wrote:
> Yes, it might bring important drawbacks: performance-wise, relatime will
> become more like atime, making it much less useful. There is also a
> significant number of desktop computers that are turned on once a day,
> the boot time may get hindered by those additional writes.
Huh? Nobody's ever claimed that atime writes cost a significant amount
of performance. The problem that relatime is designed to solve is
*spin-up* when a file is accessed.
> Actually, you are changing relatime from a boolean condition (maximum
> one additional write per write) to a atime with a coarse grain (maximum
> one additional write per day). Today you found a use case that needs a
> precision of one day. Tomorrow, someone else will find a use case that
> needs a precision of one hour. So maybe what is actually needed is a
> third option, a "grainatime" option where you can change the precision
> of the atime.
You're really over-thinking this.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-12-28 21:37 UTC|newest]
Thread overview: 15+ 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
2008-12-28 19:59 ` Matthew Garrett
2008-12-28 19:59 ` Matthew Garrett
2008-12-28 21:24 ` Éric Piel
2008-12-28 21:36 ` Matthew Wilcox [this message]
2008-12-28 21:38 ` Matthew Garrett
2008-12-28 21:38 ` Matthew Garrett
2009-01-08 12:29 ` Peter Moulder
2009-01-08 12:29 ` Peter Moulder
2009-01-08 13:32 ` Matthew Garrett
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=20081228213636.GB2002@parisc-linux.org \
--to=matthew@wil.cx \
--cc=E.A.B.Piel@tudelft.nl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/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.