All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: doiggl@velocitynet.com.au
Cc: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz
Date: Mon, 25 Aug 2014 13:35:52 +0200	[thread overview]
Message-ID: <53FB1F98.7080705@gmail.com> (raw)
In-Reply-To: <f7ff33e2237d6f316d2f8812e44e4419@mail.velocitynet.com.au>

On 08/25/2014 12:53 PM, doiggl@velocitynet.com.au wrote:
> On Mon, 25 Aug 2014 02:57:29 +0400, Ivan Shapovalov <intelfx100@gmail.com>
> wrote:
>> On Sunday 24 August 2014 at 18:09:13, doiggl@velocitynet.com.au wrote:	
>>> [...]
>>>
>>> Hello,
>>> Thanks for the details.
>>>
>>> rpms did build with following patches applied:
>>>          reiser4-for-3.15.1.patch
>>>          3.15.1-reiser4-basic-discard-support.patch
>>>
>>> see link to built rpms url [with above patches applied]
>>>
> https://build.opensuse.org/package/binaries/home:doiggl/kernel-reiser4?repository=openSUSE_13.1
>>> Question:
>>> Which "in-flight" patchsets can be applied on top of discard support
>>> patch
>>> ?
>>> Url link to patch appreciated.
>> Why do you ask? Do you want to build a general-purpose kernel with these
>> patches
>> or just help with testing?
>> Anyway,
>>
>> this is a last bugfix patch from Edward (on top of 3.15):
>>
>> - [patch 1/1] reiser4: implement ->remount_fs() super operation
>> http://www.spinics.net/lists/reiserfs-devel/msg04193.html
>>
>> and these are three patchsets that can be applied but are _unreviewed_
>> (on top of 3.15 + basic discard support):
>>
>> - [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl):
>> initial implementation.
>> http://www.spinics.net/lists/reiserfs-devel/msg04166.html
>>
>> - [PATCH 0/2] reiser4: block deallocation fixes.
>> http://www.spinics.net/lists/reiserfs-devel/msg04177.html
>>
>> - [PATCH 0/3] reiser4: space grabbing fixes.
>> http://www.spinics.net/lists/reiserfs-devel/msg04180.html
>>
>> Hope that helps,
> Hello,
>
> RE:Why do you ask? Do you want to build a general-purpose kernel with
> these patches or just help with testing?
> Answer: I wanted to access a separate disk with a existing reiser4
> partition on it. But thats another saga-storey.


Then you don't need those patches.
Wait for the new stuff at
https://sourceforge.net/projects/reiser4/files/reiser4-for-linux-3.x/
https://sourceforge.net/projects/reiser4/files/patches/

Edward.


>
> Questions:
> - Is the listing below correct ?
> - Are all 9 patches needed to put in place "batch discard support (FITRIM
> ioctl)"
>
> [RFC] [PATCHv3 1/9] reiser4: block_alloc: add BA_SOME_SPACE flag for
> grabbing a fixed amount of space.
> ..
> ..
> [RFC] [PATCHv3 9/9] reiser4: batch discard support: honor minimal extent
> length passed from the userspace.
>
> Details
> -------
>
> - [PATCH 0/2] reiser4: block deallocation fixes.
> http://www.spinics.net/lists/reiserfs-devel/msg04177.html
>
> - [PATCH 0/3] reiser4: space grabbing fixes.
> http://www.spinics.net/lists/reiserfs-devel/msg04180.html
>
> - [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl):
> initial implementation.
> http://www.spinics.net/lists/reiserfs-devel/msg04166.html
>
> [1]
>
> [2+3+9 =14 patch files to apply] as shown below
> patch urls listing.
>
> block deallocation fixes
> ------------------------
> http://www.spinics.net/lists/reiserfs-devel/msg04177.html
>    reiser4: sanitize deallocations throughout the code.
>    reiser4: block_alloc: get rid of discard-related hack in
> reiser4_dealloc_blocks().
>    
>    [PATCH 1/2] sanitize deallocations throughout the code.
>    [PATCH 2/2] block_alloc: get rid of discard-related hack in
> reiser4_dealloc_blocks()
>
> space grabbing fixes
> --------------------
> http://www.spinics.net/lists/reiserfs-devel/msg04180.html
>    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.
>    
>    [PATCH 1/3] reiser4: block_alloc: improve error handling in
> reiser4_grab_reserved().
>    [PATCH 2/3] reiser4: block_alloc: sanitize grab_enabled modifications.
>    [PATCH 3/3] reiser4: do not mess with grab_enabled; instead, use
> BA_FORCE.
>
> [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl)
> -----------------------------------------------------------------
>
> [RFC] [PATCHv3 1/9] reiser4: block_alloc: add BA_SOME_SPACE flag for
> grabbing a fixed amount of space.
> [RFC] [PATCHv3 2/9] reiser4: block_alloc: add a "forward" parameter to
> reiser4_blocknr_hint to allocate blocks only in forward direction.
> [RFC] [PATCHv3 3/9] reiser4: txnmgr: free allocated but unneeded atom in
> atom_begin_and_assign_to_txnh().
> [RFC] [PATCHv3 4/9] reiser4: txnmgr: add reiser4_create_atom() which
> creates an empty atom without capturing any nodes.
> [RFC] [PATCHv3 5/9] reiser4: txnmgr: call reiser4_post_write_back_hook()
> also for empty atoms.
> [RFC] [PATCHv3 6/9] reiser4: batch discard support: add a dummy FITRIM
> ioctl handler for directories.
> [RFC] [PATCHv3 7/9] reiser4: batch discard support: actually implement the
> FITRIM ioctl handler.
> [RFC] [PATCHv3 8/9] reiser4: block_alloc: add a "min_len" parameter to
> reiser4_blocknr_hint to limit allocated extent length from below.
> [RFC] [PATCHv3 9/9] reiser4: batch discard support: honor minimal extent
> length passed from the userspace.
>
> http://www.spinics.net/lists/reiserfs-devel/
> msg04167.html
> msg04168.html
> msg04169.html
> msg04171.html
> msg04172.html
> msg04173.html
> msg04174.html
> msg04175.html
>
> Thanks for your help and time.
> Cheers Glenn
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2014-08-25 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  7:42 Which patches can be applied on top of reiser4-for-3.15.1.patch.gz doiggl
2014-08-20  8:14 ` Ivan Shapovalov
2014-08-24  8:09   ` doiggl
2014-08-24 22:57     ` Ivan Shapovalov
2014-08-25 10:53       ` doiggl
2014-08-25 11:35         ` Edward Shishkin [this message]
2014-08-25 13:56           ` doiggl

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=53FB1F98.7080705@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=doiggl@velocitynet.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.