linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Cc: Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2] ext2, ext3: speed up file create workloads
Date: Tue, 07 Dec 2010 11:47:51 -0600	[thread overview]
Message-ID: <4CFE7347.8030807@redhat.com> (raw)

The addition of 64k block capability in the rec_len_from_disk
and rec_len_to_disk functions added a bit of math overhead which
slows down file create workloads needlessly when the architecture
cannot even support 64k blocks, thanks to page size limits.

The directory entry checking can also be optimized a bit
by sprinkling in some unlikely() conditions to move the
error handling out of line.

These 2 patches speed up a bonnie++ file creation workload for
me by several percent on ext2 & ext3.

Thanks,
-Eric

             reply	other threads:[~2010-12-07 17:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 17:47 Eric Sandeen [this message]
2010-12-07 17:51 ` [PATCH 1/2] ext2: speed up file creates by optimizing rec_len functions Eric Sandeen
2010-12-07 21:07   ` Andrew Morton
2010-12-07 21:22     ` Eric Sandeen
2010-12-07 21:33       ` Andrew Morton
2010-12-07 21:36         ` Eric Sandeen
2010-12-08 19:01         ` Andreas Dilger
2010-12-08 21:07           ` Eric Sandeen
2010-12-08 21:44             ` Andreas Dilger
2010-12-09  1:06               ` Ric Wheeler
2010-12-10 17:55                 ` Ted Ts'o
2010-12-10 18:05                   ` Ric Wheeler
2010-12-10 23:40                   ` Andreas Dilger
2010-12-11  0:24                     ` Eric Sandeen
2010-12-09  2:13               ` Eric Sandeen
2010-12-07 17:55 ` [PATCH 2/2] ext3: " Eric Sandeen
2011-01-06 14:47 ` [PATCH 0/2] ext2, ext3: speed up file create workloads Jan Kara

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=4CFE7347.8030807@redhat.com \
    --to=sandeen@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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).