All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"sct@redhat.com" <sct@redhat.com>,
	"adilger@sun.com" <adilger@sun.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"Bityutskiy Artem (Nokia-D/Helsinki)"
	<Artem.Bityutskiy@nokia.com>
Subject: Re: [PATCH 1/2] HACK: ext3: mount fast even when recovering
Date: Wed, 15 Jul 2009 18:35:38 +0300	[thread overview]
Message-ID: <4A5DF74A.8090607@nokia.com> (raw)
In-Reply-To: <20090714223649.GJ10131@mit.edu>

Theodore Tso wrote:
> On Tue, Jul 14, 2009 at 04:46:37PM -0500, Eric Sandeen wrote:
>> (whoa, can barriers make something faster?  who woulda thunk it)
> 
> I sent this reply in response to the first Adrian's first e-mail, that
> had bogus e-mail addresses for akpm and sct, so resending it here:

Sorry about that.

> Have you actually benchmarked these patches, ideally with a fixed
> filesystem image so the two runs are done requiring exactly the same
> number of blocks to recover?  We implement ordered I/O in terms of
> doing a flush, so it would be surprising to see that a significant
> difference in times.  Also, it would be useful to do a blktrace before
> and after your patches, again with a fixed filesystem image so the
> experiment can be carefully controlled.

Yes the I/O is no faster.

The hacks just make the file system available for reading while recovery I/O
is ongoing.

Attempts to write are likely to block (even buffered I/O must wait for
locked buffers).

I will send some examples.

  reply	other threads:[~2009-07-15 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 14:05 [PATCH 0/2] ext3 HACKs Adrian Hunter
2009-07-14 14:05 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:34   ` Andrew Morton
2009-07-14 21:46     ` Eric Sandeen
2009-07-14 22:36       ` Theodore Tso
2009-07-15 15:35         ` Adrian Hunter [this message]
2009-07-15  5:53     ` Artem Bityutskiy
2009-07-15 15:35     ` Adrian Hunter
2009-07-14 14:06 ` [PATCH 2/2] HACK: do I/O read requests while ext3 journal recovers Adrian Hunter
  -- strict thread matches above, loose matches on Subject: below --
2009-07-14 14:02 [PATCH 0/2] ext3 HACKs Adrian Hunter
2009-07-14 14:03 ` [PATCH 1/2] HACK: ext3: mount fast even when recovering Adrian Hunter
2009-07-14 21:22   ` Andreas Dilger
2009-07-15 15:35     ` Adrian Hunter

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=4A5DF74A.8090607@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sct@redhat.com \
    --cc=tytso@mit.edu \
    /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.