From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Frans Meulenbroeks" <fransmeulenbroeks@gmail.com>
Cc: "Nye Liu" <nyet@mrv.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Nye Liu" <nyet@nyet.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] INITRAMFS: Add option to preserve mtime from INITRAMFS cpio images
Date: Fri, 05 Sep 2008 01:08:32 +0200 [thread overview]
Message-ID: <m3abenzez3.fsf@maximus.localdomain> (raw)
In-Reply-To: <ac9c93b10809040011h19b70715ge2ba06372f1b0fe0@mail.gmail.com> (Frans Meulenbroeks's message of "Thu\, 4 Sep 2008 09\:11\:42 +0200")
"Frans Meulenbroeks" <fransmeulenbroeks@gmail.com> writes:
> "Invaluable" != "nice to know".
Well, I guess it's as "invaluable" for embedded systems running on
initramfs as mtime on regular filesystems in case of normal systems.
Is mtime on ext3 "invaluable" or just "nice to know"?
> I admit that the net effect of this on boot time is marginal (but some
> might consider having mtime a marginal benefit), and 100 cents also
> make a dollar, so my suggestion would be to either reject this patch
> or make it optional (e.g. depending on some debug config flag).
It depends on how marginal is it. If it makes unpacking 1% slower I
can see no need for being optional. 10% - maybe it should?
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-09-04 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:52 Nye Liu
2008-08-16 8:58 ` Andrew Morton
2008-09-03 20:29 ` Nye Liu
2008-09-03 22:22 ` Andrew Morton
2008-09-03 22:31 ` Nye Liu
2008-09-03 22:36 ` Andrew Morton
2008-09-04 7:11 ` Frans Meulenbroeks
2008-09-04 7:13 ` nyet
2008-09-04 23:08 ` Krzysztof Halasa [this message]
2008-09-03 22:41 ` Nye Liu
2008-09-03 22:48 ` Andrew Morton
2008-09-03 22:53 ` Nye Liu
2008-09-03 22:54 ` Nye Liu
2008-09-03 23:04 ` Nye Liu
2008-09-03 23:19 ` Andrew Morton
2008-09-03 23:30 ` Nye Liu
[not found] ` <20080903164144.27c94bae.akpm@linux-foundation.org>
2008-09-04 1:40 ` [PATCH] INITRAMFS: Preserve " Nye Liu
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=m3abenzez3.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@linux-foundation.org \
--cc=fransmeulenbroeks@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nyet@mrv.com \
--cc=nyet@nyet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®