linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@kepstin.ca>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Boot speed/mount time regression with 3.4.0-rc2
Date: Tue, 10 Apr 2012 12:04:00 -0400	[thread overview]
Message-ID: <1334073840.2758.5.camel@ayu> (raw)
In-Reply-To: <20120410151645.GC2296@localhost.localdomain>

On Tue, 2012-04-10 at 11:16 -0400, Josef Bacik wrote:
> On Mon, Apr 09, 2012 at 05:20:46PM -0400, Calvin Walton wrote:
> > On Mon, 2012-04-09 at 16:54 -0400, Josef Bacik wrote:
> > > On Mon, Apr 09, 2012 at 01:10:04PM -0400, Calvin Walton wrote:
> > > > On Mon, 2012-04-09 at 11:53 -0400, Calvin Walton wrote:
> > > > > Hi,
> > > > > 
> > > > > I have a system that's using a dracut-generated initramfs to mount a
> > > > > btrfs root. After upgrading to kernel 3.4.0-rc2 to test it out, I've
> > > > > noticed that the process of mounting the root filesystem takes much
> > > > > longer with 3.4.0-rc2 than it did with 3.3.1 - nearly 30 seconds slower!
> 
> Ok drop that previous patch and give this one a whirl, it helped on my laptop.
> This is only  half of the problem AFAICS, but it's the easier half to fix, in
> the meantime I need to lock down why we're not writing out cache for a bunch of
> block groups, but thats trickier since the messages I need are spit out while
> I'm shutting down, so I need to get creative.  Let me know if/how much this
> helps.  Thanks,

This one brings the mount time right down on my laptop, it's back to
around 0.5 seconds, same as 3.3.x.

Tested-by: Calvin Walton <calvin.walton@kepstin.ca>

I'll keep following this email thread; let me know if you have any other
patches that you want me to try out.

-- 
Calvin Walton <calvin.walton@kepstin.ca>


  reply	other threads:[~2012-04-10 16:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09 15:53 Boot speed/mount time regression with 3.4.0-rc2 Calvin Walton
2012-04-09 16:08 ` cwillu
2012-04-09 17:10 ` Calvin Walton
2012-04-09 17:14   ` Josef Bacik
2012-04-09 20:54   ` Josef Bacik
2012-04-09 21:20     ` Calvin Walton
2012-04-10 13:08       ` Josef Bacik
2012-04-10 15:16       ` Josef Bacik
2012-04-10 16:04         ` Calvin Walton [this message]
2012-04-10 16:29           ` David Sterba
2012-04-10 16:34             ` Calvin Walton
2012-04-11 15:26         ` Ahmet Inan
2012-04-11 17:04           ` Josef Bacik
2012-04-12  9:22             ` Ahmet Inan
2012-04-12 13:37               ` Josef Bacik
2012-04-12 14:23                 ` Josef Bacik
2012-04-13  6:26                   ` Ahmet Inan
2012-04-13  6:49                     ` cwillu
2012-04-13 11:22                       ` Ahmet Inan
     [not found]                         ` <CAFDW0jKMEQ+oMN41euh1cMy4h+6Qntt5UL9+0HZw4r9SpDJVvQ@mail.gmail.com>
2012-04-13 12:57                           ` cwillu
2012-04-13 13:20                             ` Ahmet Inan
2012-04-13 13:47                           ` Josef Bacik
2012-04-21 20:54                             ` Ahmet Inan
2012-04-22  7:59                               ` Sergei Trofimovich
2012-04-22  9:16                                 ` Ahmet Inan
2012-04-22 13:57                                   ` Ahmet Inan
2012-05-03 13:40                               ` Ahmet Inan
2012-04-11 16:38 ` Chester
2012-04-11 18:24   ` Josef Bacik

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=1334073840.2758.5.camel@ayu \
    --to=calvin.walton@kepstin.ca \
    --cc=chris.mason@oracle.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).