All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Bernhard Kraft <kraftb@think-open.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2/3/4 performance issue
Date: Sun, 10 May 2015 17:56:07 -0400	[thread overview]
Message-ID: <20150510215607.GA14298@thunk.org> (raw)
In-Reply-To: <554F1045.4070105@think-open.at>

On Sun, May 10, 2015 at 10:01:09AM +0200, Bernhard Kraft wrote:
> 
> I work on implementing the ext2 filesystem for a PIC microcontroller and
> while reading the sources of it in the linux kernel I stumbled upon the
> following performance issue.....

Your observations are currect as far as ext2 is concerned; by the time
you get to ext4, it's a bit more complicated.  Also, the
extN_bg_has_super() has in general not been a bottleneck, at least on
modern CPUs.  Perhaps it would be more of an issue on a PIC
microcontroller, of course.

Finally, note that the overhead is cached so it is only calculated the
first time the extN_statfs() is called.

Cheers,

					- Ted

      reply	other threads:[~2015-05-10 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10  8:01 ext2/3/4 performance issue Bernhard Kraft
2015-05-10 21:56 ` Theodore Ts'o [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=20150510215607.GA14298@thunk.org \
    --to=tytso@mit.edu \
    --cc=kraftb@think-open.at \
    --cc=linux-kernel@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 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.