reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Shapovalov <intelfx100@gmail.com>
To: reiserfs-devel@vger.kernel.org
Cc: Ivan Shapovalov <intelfx100@gmail.com>
Subject: [PATCH 0/6] reiser4: discard support: "precise discard" aka padding of extents to erase unit boundaries.
Date: Sat, 13 Dec 2014 00:10:26 +0300	[thread overview]
Message-ID: <1418418632-18396-1-git-send-email-intelfx100@gmail.com> (raw)

So, this patchset uses your algorithm of padding/gluing extents to be discarded.
I've added exact allocation primitives (is it what you've been talking about?),
made the discard procedure allocate blocks of all paddings it performs and
fixed an apparent bug in extent gluing which triggered the "edward-1635"
assertion.

Edward Shishkin (1):
  reiser4: iterate over extents in discard_atom

Ivan Shapovalov (5):
  reiser4: block_alloc: split block allocation accounting logic into separate functions for re-use.
  reiser4: block_alloc, plugin/space/bitmap: add a method for "exact" block allocation.
  reiser4: discard: don't be overly smart when gluing extents in discard_sorted_merged_extents().
  reiser4: blocknrlist: add operations blocknr_list_del() and blocknr_list_update_extent().
  reiser4: discard: allocate extent paddings.

 fs/reiser4/block_alloc.c                  | 175 +++++++++----
 fs/reiser4/block_alloc.h                  |   3 +
 fs/reiser4/blocknrlist.c                  |  38 +++
 fs/reiser4/discard.c                      | 410 +++++++++++++++++++++++++++---
 fs/reiser4/discard.h                      |   8 +-
 fs/reiser4/forward.h                      |   1 +
 fs/reiser4/init_super.c                   |   4 +
 fs/reiser4/plugin/space/bitmap.c          |  94 +++++--
 fs/reiser4/plugin/space/bitmap.h          |   3 +
 fs/reiser4/plugin/space/space_allocator.h |  10 +-
 fs/reiser4/super.h                        |   4 +
 fs/reiser4/txnmgr.h                       |   6 +
 12 files changed, 647 insertions(+), 109 deletions(-)

-- 
2.1.3


             reply	other threads:[~2014-12-12 21:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 21:10 Ivan Shapovalov [this message]
2014-12-12 21:10 ` [PATCH 1/6] reiser4: block_alloc: split block allocation accounting logic into separate functions for re-use Ivan Shapovalov
2014-12-12 21:10 ` [PATCH 2/6] reiser4: block_alloc, plugin/space/bitmap: add a method for "exact" block allocation Ivan Shapovalov
2014-12-19 15:43   ` Edward Shishkin
2014-12-12 21:10 ` [PATCH 3/6] reiser4: iterate over extents in discard_atom Ivan Shapovalov
2014-12-12 21:10 ` [PATCH 4/6] reiser4: discard: don't be overly smart when gluing extents in discard_sorted_merged_extents() Ivan Shapovalov
2014-12-19 20:24   ` Edward Shishkin
2014-12-12 21:10 ` [PATCH 5/6] reiser4: blocknrlist: add operations blocknr_list_del() and blocknr_list_update_extent() Ivan Shapovalov
2014-12-12 21:10 ` [PATCH 6/6] reiser4: discard: allocate extent paddings Ivan Shapovalov
2014-12-13 22:38 ` [PATCH 0/6] reiser4: discard support: "precise discard" aka padding of extents to erase unit boundaries Edward Shishkin
2014-12-14  8:03   ` Ivan Shapovalov
2014-12-15 19:30     ` Edward Shishkin
2014-12-19 15:46       ` Edward Shishkin

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=1418418632-18396-1-git-send-email-intelfx100@gmail.com \
    --to=intelfx100@gmail.com \
    --cc=reiserfs-devel@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).