From: Theodore Tso <tytso@mit.edu>
To: Alexander Shishkin <alexander.shishckin@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org
Subject: Re: [Q] ext3 mkfs: zeroing journal blocks
Date: Tue, 12 May 2009 17:04:46 -0400 [thread overview]
Message-ID: <20090512210446.GD23773@mit.edu> (raw)
In-Reply-To: <71a0d6ff0905120549h628146d8p3def31b09b79199a@mail.gmail.com>
On Tue, May 12, 2009 at 03:49:30PM +0300, Alexander Shishkin wrote:
>
> So, what Andreas explained yesterday also applies to the internal log
> case. I see. Would you say it's possible to prevent this, for instance
> somehow say, by means checksums as Andreas suggested?
>
It's *possible*, but it's not a trivial amount of work; it requires
both kernel and userspace changes, though.
> It's an mmc and it (mkfs) runs almost two times faster without zeroing
> the journal. The only thing I'm worried about is the time that it
> takes for mke2fs -j to complete. I've done some caching trickery to
> unix_io.c which I'm going to post here separately, but most of the
> time seems to be taken by the journal.
But why do you care about the time it akes for mke2fs -j to complete?
How much time is it taking? Normally mke2fs isn't one of those
programs which gets run all the time....
- Ted
next prev parent reply other threads:[~2009-05-12 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 15:03 [Q] ext3 mkfs: zeroing journal blocks Alexander Shishkin
2009-05-11 17:58 ` Eric Sandeen
2009-05-11 18:20 ` Andreas Dilger
2009-05-11 18:44 ` Eric Sandeen
2009-05-11 19:35 ` Theodore Tso
2009-05-11 19:35 ` Andreas Dilger
2009-05-12 11:55 ` Alexander Shishkin
2009-05-12 12:13 ` Theodore Tso
2009-05-12 12:49 ` Alexander Shishkin
2009-05-12 21:04 ` Theodore Tso [this message]
2009-07-29 15:58 ` [PATCH] [RFC] mkjournal: zero journal blocks only when necessary Alexander Shishkin
2009-07-29 17:16 ` Theodore Tso
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=20090512210446.GD23773@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=alexander.shishckin@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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).