linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: [PATCH 0/3] Clean up the EXT4_STATE_DELALLOC_RESERVED state flag
Date: Tue,  2 Sep 2014 18:05:46 -0400	[thread overview]
Message-ID: <1409695549-18605-1-git-send-email-tytso@mit.edu> (raw)

This is another in the series of cleanup patches that address some
long-standing nits/annoyances in the ext4 code base.

I'm sure it won't last, since there are some feature patches being
worked on, but the ext4 tree is currently 500 lines of code lighter than
at the beginning of this development cycle (and this is including the
200 lines added to support /proc/fs/ext4/.../es_shrinker_info).   Most
of the savings came from Dmitry's refactor of ext4_move_extents().

Theodore Ts'o (3):
  ext4: pass allocation_request struct to ext4_(alloc,splice)_branch
  ext4: prepare to drop EXT4_STATE_DELALLOC_RESERVED
  ext4: drop the EXT4_STATE_DELALLOC_RESERVED flag

 fs/ext4/balloc.c   |  3 +-
 fs/ext4/ext4.h     |  1 -
 fs/ext4/extents.c  |  6 +++-
 fs/ext4/indirect.c | 86 ++++++++++++++++++++++++++----------------------------
 fs/ext4/inode.c    | 20 +++----------
 fs/ext4/mballoc.c  | 12 ++------
 fs/ext4/xattr.c    |  6 ----
 7 files changed, 54 insertions(+), 80 deletions(-)

-- 
2.1.0


             reply	other threads:[~2014-09-02 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 22:05 Theodore Ts'o [this message]
2014-09-02 22:05 ` [PATCH 1/3] ext4: pass allocation_request struct to ext4_(alloc,splice)_branch Theodore Ts'o
2014-09-03 16:25   ` Jan Kara
2014-09-03 17:17     ` Theodore Ts'o
2014-09-02 22:05 ` [PATCH 2/3] ext4: prepare to drop EXT4_STATE_DELALLOC_RESERVED Theodore Ts'o
2014-09-03 16:26   ` Jan Kara
2014-09-02 22:05 ` [PATCH 3/3] ext4: drop the EXT4_STATE_DELALLOC_RESERVED flag Theodore Ts'o
2014-09-03 16:26   ` 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=1409695549-18605-1-git-send-email-tytso@mit.edu \
    --to=tytso@mit.edu \
    --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).