linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: tytso@mit.edu, darrick.wong@oracle.com
Cc: linux-ext4@vger.kernel.org
Subject: [PATCH 0/6] e2fsprogs Summer 2014 patchbomb, part 5
Date: Fri, 08 Aug 2014 21:26:10 -0700	[thread overview]
Message-ID: <20140809042610.2441.6868.stgit@birch.djwong.org> (raw)

Hi all,

This is part 5 of the Summer 2014 e2fsprogs patchset.  Whereas all the
patches I've sent previously were to fix problems in the library and
e2fsck uncovered by the e2fuzz metadata fuzzer, we're now to the part
of the patch set that includes new features.  I'm only posting things
that have been discussed recently; the other "new" features (that have
been out for review for quite some time) haven't changed since May.
They'll be in part 6, which I'm holding onto until Ted has a chance to
look at the inline data pile of stuff.

The first new feature was suggested by Pu Hou -- the ability to create
inline data symlinks.  That's patch 1, and it requires the patches in
part 4 + the v2 patches I sent out today.

Patch 2 fixes a number of gcc warnings.

Patch 3-6 implement v2 of the e2fsck readahead functionality, which
promises to reduce fsck runtime by 10-30%.  You might want to read
the report: http://marc.info/?l=linux-ext4&m=140755433701165&w=2
("e2fsck readahead speedup performance report") for all the juicy
details!

I've tested these e2fsprogs changes against the -next branch as of
8/4.  The patches follow the end of "Summer 2014 patchbomb part 4",
and have been tested against the 'make check' suite.

Comments and questions are, as always, welcome.

--D

             reply	other threads:[~2014-08-09  4:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09  4:26 Darrick J. Wong [this message]
2014-08-09  4:26 ` [PATCH 1/6] libext2fs: create inlinedata symlinks Darrick J. Wong
2014-08-24 16:15   ` Theodore Ts'o
2014-08-09  4:26 ` [PATCH 2/6] misc: fix gcc warnings Darrick J. Wong
2014-08-24 16:24   ` Theodore Ts'o
2014-08-09  4:26 ` [PATCH 3/6] mke2fs: set block_validity as a default mount option Darrick J. Wong
2014-08-24 22:47   ` Theodore Ts'o
2014-08-25 15:52     ` Darrick J. Wong
2014-08-25 16:36       ` [PATCH] ext4: enable block_validity by default Darrick J. Wong
2014-09-02  2:02         ` Theodore Ts'o
2014-08-09  4:26 ` [PATCH 4/6] ext2fs: add readahead method to improve scanning Darrick J. Wong
2014-08-09  4:26 ` [PATCH 5/6] libext2fs/e2fsck: provide routines to read-ahead metadata Darrick J. Wong
2014-08-11  5:21   ` Darrick J. Wong
2014-08-11  6:24     ` Theodore Ts'o
2014-08-11  6:31       ` Darrick J. Wong
2014-08-11 14:34         ` Theodore Ts'o
2014-08-11 18:05           ` Darrick J. Wong
2014-08-11 18:32             ` Theodore Ts'o
2014-08-11 18:55               ` Darrick J. Wong
2014-08-11 20:10                 ` Theodore Ts'o
2014-08-11 20:50                   ` Darrick J. Wong
2014-08-09  4:26 ` [PATCH 6/6] e2fsck: read-ahead metadata during passes 1, 2, and 4 Darrick J. Wong
2014-08-09  5:53 ` [PATCH 0/6] e2fsprogs Summer 2014 patchbomb, part 5 Theodore Ts'o
2014-08-09  5:59   ` Darrick J. Wong

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=20140809042610.2441.6868.stgit@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 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).