From: Ivan Shapovalov <intelfx100@gmail.com>
To: reiserfs-devel@vger.kernel.org
Cc: Ivan Shapovalov <intelfx100@gmail.com>
Subject: [RFC] [PATCHv4 0/4] reiser4: discard support: initial implementation.
Date: Fri, 13 Jun 2014 18:58:10 +0400 [thread overview]
Message-ID: <1402671494-24513-1-git-send-email-intelfx100@gmail.com> (raw)
...I'm back on board, now more or less till September.
v1: - initial implementation (patches 1, 2)
v2: - cleanup, fixes discovered in debug mode
- saner logging
- assertions
- enablement of discard through mount option
v3: - fixed the extent merge loop in discard_atom()
v4: - squashed fix-ups into the main patch (with exception of reiser4_debug())
- fixed bug in usage of division ops discovered while building on ARM
BTW, it seems that I've understood the logic of block allocation/deallocation
(the disk space leak problem you mentioned earlier), and... this breaks the
idea of ->discard_set (i. e. "log everything").
I'll write a follow-up once I verify the (in-)consistency of my thoughts :)
Ivan Shapovalov (4):
reiser4: discard support: make space_allocator's check_blocks() reusable.
reiser4: add reiser4_debug(): a conditional equivalent of reiser4_log().
reiser4: discard support: initial implementation using extent lists.
reiser4: discard support: enable discard functionality through a mount option.
fs/reiser4/Makefile | 1 +
fs/reiser4/block_alloc.c | 38 ++-
fs/reiser4/block_alloc.h | 14 +-
fs/reiser4/debug.h | 4 +
fs/reiser4/dformat.h | 2 +
fs/reiser4/discard.c | 488 ++++++++++++++++++++++++++++++
fs/reiser4/discard.h | 38 +++
fs/reiser4/forward.h | 1 +
fs/reiser4/init_super.c | 2 +
fs/reiser4/plugin/space/bitmap.c | 81 +++--
fs/reiser4/plugin/space/bitmap.h | 2 +-
fs/reiser4/plugin/space/space_allocator.h | 4 +-
fs/reiser4/super.h | 4 +-
fs/reiser4/txnmgr.c | 19 ++
fs/reiser4/txnmgr.h | 5 +
fs/reiser4/znode.c | 9 +-
16 files changed, 657 insertions(+), 55 deletions(-)
create mode 100644 fs/reiser4/discard.c
create mode 100644 fs/reiser4/discard.h
--
2.0.0
next reply other threads:[~2014-06-13 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 14:58 Ivan Shapovalov [this message]
2014-06-13 14:58 ` [RFC] [PATCHv4 1/4] reiser4: discard support: make space_allocator's check_blocks() reusable Ivan Shapovalov
2014-06-13 14:58 ` [RFC] [PATCHv4 2/4] reiser4: add reiser4_debug(): a conditional equivalent of reiser4_log() Ivan Shapovalov
2014-06-13 14:58 ` [RFC] [PATCHv4 3/4] reiser4: discard support: initial implementation using extent lists Ivan Shapovalov
2014-06-13 14:58 ` [RFC] [PATCHv4 4/4] reiser4: discard support: enable discard functionality through a mount option Ivan Shapovalov
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=1402671494-24513-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).