From: Edward Shishkin <edward.shishkin@gmail.com>
To: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: [PATCHv2 0/3] reiser4: space grabbing fixes.
Date: Wed, 10 Dec 2014 13:52:08 +0100 [thread overview]
Message-ID: <548841F8.4010409@gmail.com> (raw)
In-Reply-To: <5497656.EllimmOa76@intelfx-laptop>
On 12/10/2014 01:27 PM, Ivan Shapovalov wrote:
> On Thursday 23 October 2014 at 11:18:02, Ivan Shapovalov wrote:
>> These are mostly equivalent transformations (aside from the first patch)
>> I've done when I was experimenting with rwsems at zero-th iteration of
>> batch discard support.
>>
>> v2: - disable grab in current context unconditionally, not only if !BA_FORCE
>>
>> Ivan Shapovalov (3):
>> reiser4: block_alloc: improve error handling in reiser4_grab_reserved().
>> reiser4: block_alloc: sanitize grab_enabled modifications.
>> reiser4: do not mess with grab_enabled; instead, use BA_FORCE.
>>
>> fs/reiser4/block_alloc.c | 57 +++++++++++++++++---------------
>> fs/reiser4/plugin/file/file.c | 12 +++----
>> fs/reiser4/plugin/file/file_conversion.c | 3 +-
>> fs/reiser4/plugin/file/tail_conversion.c | 11 +++---
>> fs/reiser4/plugin/item/extent_file_ops.c | 3 +-
>> fs/reiser4/plugin/item/tail.c | 3 +-
>> fs/reiser4/safe_link.c | 4 +--
>> 7 files changed, 44 insertions(+), 49 deletions(-)
> ping, what's the status?
This is in "upstream" already.
>
> /*
> I'll send another round of discard patches shortly... That is, once I figure
> out how to explain in comments the sheer amount of happily coinciding subtle
> details, whose coincidence makes everything actually work. :/
Note, that basic discard stuff is also in "upstream".
So, please, make sure that your patches are "re-based"
>
> BTW, could you please check that I've rebased your "precise discard" patch
> correctly?
> https://github.com/intelfx/linux/commit/47f27446d5ae7b796a842735811c48cc07615dd6
> */
>
I suggest to start with implementing the bitmap primitives that
I talked about. Just to avoid extra-work..
Thanks,
Edward.
next prev parent reply other threads:[~2014-12-10 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 7:18 [PATCHv2 0/3] reiser4: space grabbing fixes Ivan Shapovalov
2014-10-23 7:18 ` [PATCHv2 1/3] reiser4: block_alloc: improve error handling in reiser4_grab_reserved() Ivan Shapovalov
2014-10-23 7:18 ` [PATCHv2 2/3] reiser4: block_alloc: sanitize grab_enabled modifications Ivan Shapovalov
2014-11-16 5:38 ` Ivan Shapovalov
2014-11-16 9:53 ` Edward Shishkin
2014-11-16 10:45 ` Edward Shishkin
2014-11-16 11:49 ` Edward Shishkin
2014-11-16 10:45 ` Edward Shishkin
2014-11-19 1:39 ` Ivan Shapovalov
2014-10-23 7:18 ` [PATCHv2 3/3] reiser4: do not mess with grab_enabled; instead, use BA_FORCE Ivan Shapovalov
2014-10-23 7:20 ` [PATCHv2 0/3] reiser4: space grabbing fixes Ivan Shapovalov
2014-12-10 12:27 ` Ivan Shapovalov
2014-12-10 12:52 ` Edward Shishkin [this message]
2014-12-10 13:30 ` Ivan Shapovalov
2014-12-10 21:51 ` Edward Shishkin
2014-12-12 22:19 ` Ivan Shapovalov
2014-12-13 23:41 ` 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=548841F8.4010409@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=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).