linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Christian Rohmann <crohmann@netcologne.de>,
	Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Progress indicator when (slowly) mounting a btrfs filesystem?
Date: Mon, 1 Feb 2016 09:19:31 -0500	[thread overview]
Message-ID: <56AF6973.5070809@gmail.com> (raw)
In-Reply-To: <56AF659E.2080009@netcologne.de>

On 2016-02-01 09:03, Christian Rohmann wrote:
> Hey Chris,
>
> On 01/28/2016 12:47 AM, Chris Murphy wrote:
>> Might be a bug, but more likely might be a lack of optimization. If it
>> eventually mounts without errors that's a pretty good plus. Lots of
>> file systems can't handle power failures well at all.
>
> So what and how should I go about profiling such a long running mount in
> order to help finding point where optimization is needed the most then?
It would probably require some work with perf and ftrace, which means 
you likely need to build a special kernel just for testing, and then 
generate an ideally clean-room like environment (whatever hosting, plus 
userspace, plus a consistent filesystem image that you can reuse for 
each test, etc).

Kernel profiling is a decidedly non-trivial task, and is not something I 
would recommend somebody try unless both:
a) They already have a working knowledge of kernel internals, or are 
willing to learn.
b) They have the time and resources to do it right in a reproducible manner.

      reply	other threads:[~2016-02-01 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 16:24 Progress indicator when (slowly) mounting a btrfs filesystem? Christian Rohmann
2016-01-27 21:00 ` bbrendon
2016-01-27 23:47 ` Chris Murphy
2016-02-01 14:03   ` Christian Rohmann
2016-02-01 14:19     ` Austin S. Hemmelgarn [this message]

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=56AF6973.5070809@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=crohmann@netcologne.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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).