Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[doiggl]

Hello,

Which patches can be applied on top of reiser4-for-3.15.1.patch.gz
2014-08-09 616.4 kB 
I see this listing[1]  [sorted by date] in
http://www.spinics.net/lists/reiserfs-devel/maillist.html
Thanks Glenn

[1] long patch listing based on date.
extracted via  # grep -i PATCHv listing.txt  | grep -i reiser4:| more

Re: [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl):
initial implementation.
[RFC] [PATCHv3 9/9] reiser4: batch discard support: honor minimal extent
length passed from the userspace.
[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 7/9] reiser4: batch discard support: actually implement the
FITRIM ioctl handler.
[RFC] [PATCHv3 6/9] reiser4: batch discard support: add a dummy FITRIM
ioctl handler for directories.
[RFC] [PATCHv3 5/9] reiser4: txnmgr: call reiser4_post_write_back_hook()
also for empty atoms.
[RFC] [PATCHv3 4/9] reiser4: txnmgr: add reiser4_create_atom() which
creates an empty atom without capturing any nodes.
[RFC] [PATCHv3 3/9] reiser4: txnmgr: free allocated but unneeded atom in
atom_begin_and_assign_to_txnh().
[RFC] [PATCHv3 2/9] reiser4: block_alloc: add a "forward" parameter to
reiser4_blocknr_hint to allocate blocks only in forward direction.
[RFC] [PATCHv3 1/9] reiser4: block_alloc: add BA_SOME_SPACE flag for
grabbing a fixed amount of space.
[RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl): initial
implementation.
Re: [RFC] [PATCHv2 0/7] reiser4: batch discard support (FITRIM ioctl):
initial implementation.
Re: [RFC] [PATCHv2 0/7] reiser4: batch discard support (FITRIM ioctl):
initial implementation.
[RFC] [PATCHv2 7/7] reiser4: batch discard support: actually implement the
FITRIM ioctl handler.
[RFC] [PATCHv2 6/7] reiser4: batch discard support: add a dummy FITRIM
ioctl handler for directories.
[RFC] [PATCHv2 5/7] reiser4: txnmgr: call reiser4_post_write_back_hook()
also for empty atoms.
[RFC] [PATCHv2 4/7] reiser4: txnmgr: add reiser4_create_atom() which
creates an empty atom without capturing any nodes.
[RFC] [PATCHv2 3/7] reiser4: txnmgr: free allocated but unneeded atom in
atom_begin_and_assign_to_txnh().
[RFC] [PATCHv2 2/7] reiser4: block_alloc: add a "forward" parameter to
reiser4_blocknr_hint to allocate blocks only in forward direction.
[RFC] [PATCHv2 1/7] reiser4: block_alloc: add BA_SOME_SPACE flag for
grabbing a fixed amount of space.
[RFC] [PATCHv2 0/7] reiser4: batch discard support (FITRIM ioctl): initial
implementation.
Re: [PATCHv2 0/3] reiser4: discard support: perform discard before all
deallocations.
Re: [PATCHv2 0/3] reiser4: discard support: perform discard before all
deallocations.
Re: [PATCHv7 0/6] reiser4: discard support: simplified and race-free
initial implementation.
[PATCHv7 6/6] reiser4: discard support: initial implementation using
blocknr_list, without extent padding.
[PATCHv7 5/6] reiser4: blocknr_set: use kmem_cache instead of kmalloc for
allocating entries.
[PATCHv7 3/6] reiser4: add an implementation of "block lists", splitted
off the discard code.
[PATCHv7 4/6] reiser4: blocknr_list: use kmem_cache instead of kmalloc for
allocating entries.
[PATCHv7 2/6] reiser4: make space_allocator's check_blocks() reusable.
[PATCHv7 1/6] reiser4: fix reiser4_post_{commit,write_back}_hook() and
their invocations.
[PATCHv7 0/6] reiser4: discard support: simplified and race-free initial
implementation.
Re: [PATCHv2 0/3] reiser4: discard support: perform discard before all
deallocations.
Re: [PATCHv2 0/3] reiser4: discard support: perform discard before all
deallocations.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
[PATCHv2 3/3] reiser4: discard support: perform discard before all
deallocations.
[PATCHv2 2/3] reiser4: discard support: use reiser4_post_write_back_hook()
for discarding and completing deferred deallocations.
[PATCHv2 1/3] reiser4: fix reiser4_post_{commit,write_back}_hook() and
their invocations.
[PATCHv2 0/3] reiser4: discard support: perform discard before all
deallocations.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
Re: [PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
[PATCHv6 5/5] reiser4: blocknr_set: use kmem_cache instead of kmalloc for
allocating entries.
[PATCHv6 4/5] reiser4: blocknr_list: use kmem_cache instead of kmalloc for
allocating entries.
[PATCHv6 3/5] reiser4: discard support: initial implementation using
linked lists.
[PATCHv6 2/5] reiser4: add an implementation of "block lists", splitted
off the discard code.
[PATCHv6 1/5] reiser4: make space_allocator's check_blocks() reusable.
[PATCHv6 0/5] reiser4: discard support: initial implementation.
Re: [RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
Re: [RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
Re: [RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
Re: [RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
Re: [RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
[RFC] [PATCHv5 1/4] reiser4: make space_allocator's check_blocks()
reusable.
[RFC] [PATCHv5 3/4] reiser4: add reiser4_debug(): a conditional equivalent
of reiser4_log().
[RFC] [PATCHv5 4/4] reiser4: discard support: initial implementation using
linked lists.
[RFC] [PATCHv5 2/4] reiser4: add an implementation of "block lists",
splitted off the discard code.
[RFC] [PATCHv5 0/4] reiser4: discard support: initial implementation,
refactored.
[RFC] [PATCHv4 4/4] reiser4: discard support: enable discard functionality
through a mount option.
[RFC] [PATCHv4 3/4] reiser4: discard support: initial implementation using
extent lists.
[RFC] [PATCHv4 1/4] reiser4: discard support: make space_allocator's
check_blocks() reusable.
[RFC] [PATCHv4 2/4] reiser4: add reiser4_debug(): a conditional equivalent
of reiser4_log().
[RFC] [PATCHv4 0/4] reiser4: discard support: initial implementation.
[RFC] [PATCHv3 5/5] reiser4: discard support: downgrade all reiser4_log()
to reiser4_debug().
[RFC] [PATCHv3 4/5] reiser4: discard support: add assertions to all code
written within this feature.
[RFC] [PATCHv3 3/5] reiser4: discard support: enable discard functionality
through a mount option.
[RFC] [PATCHv3 2/5] reiser4: discard support: initial implementation using
extent lists.
[RFC] [PATCHv3 1/5] reiser4: discard support: make space_allocator's
check_blocks() reusable.
[RFC] [PATCHv3 0/5] reiser4: discard support: initial implementation.
Re: [RFC] [PATCHv2 0/5] reiser4: discard support: initial implementation.
Re: [RFC] [PATCHv2 0/5] reiser4: discard support: initial implementation.
[PATCHv2] reiser4: fix an assertion broken since 3.11.
Re: [RFC] [PATCHv2 0/5] reiser4: discard support: initial implementation.
[RFC] [PATCHv2 5/5] reiser4: discard support: downgrade all reiser4_log()
to reiser4_debug().
[RFC] [PATCHv2 4/5] reiser4: discard support: add assertions to all code
written within this feature.
[RFC] [PATCHv2 3/5] reiser4: discard support: enable discard functionality
through a mount option.
[RFC] [PATCHv2 2/5] reiser4: discard support: initial implementation using
extent lists.
[RFC] [PATCHv2 1/5] reiser4: discard support: make space_allocator's
check_blocks() reusable.
[RFC] [PATCHv2 0/5] reiser4: discard support: initial implementation.

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[Ivan Shapovalov]

[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]

On Wednesday 20 August 2014 at 17:42:52, doiggl@velocitynet.com.au wrote:	
> Hello,
> 
> Which patches can be applied on top of reiser4-for-3.15.1.patch.gz
> 2014-08-09 616.4 kB 
> I see this listing[1]  [sorted by date] in
> http://www.spinics.net/lists/reiserfs-devel/maillist.html
> Thanks Glenn

The patches marked with [RFC] are pre-experimental, that is, "request for
comments". They are not to be applied to any configuration with significant
data, not to mention in any way production systems.

Remaining ones are a bit less experimental, but anyway -- they are still up to
review. Testing is appreciated, but... it can result in anything.

Currently there are three actual patchsets "in flight":

- [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl): initial implementation.
- [PATCH 0/2] reiser4: block deallocation fixes.
- [PATCH 0/3] reiser4: space grabbing fixes.

The main discard support patchset,

- [PATCHv7 0/6] reiser4: discard support: simplified and race-free initial implementation.

is already reviewed by Edward and uploaded to sourceforge under name of
3.15.1-reiser4-basic-discard-support.patch.gz. It is to be applied on top of
reiser4-for-3.15.1.

The "in-flight" patchsets are to be applied on top of discard support patch.

Hope that helps,
-- 
Ivan Shapovalov / intelfx /

> 
> [1] long patch listing based on date.
> extracted via  # grep -i PATCHv listing.txt  | grep -i reiser4:| more
> 
> [...]
> 
> --
> 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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[doiggl]

On Wed, 20 Aug 2014 12:14:41 +0400, Ivan Shapovalov <intelfx100@gmail.com>
wrote:
> On Wednesday 20 August 2014 at 17:42:52, doiggl@velocitynet.com.au
wrote:	
>> Hello,
>> 
>> Which patches can be applied on top of reiser4-for-3.15.1.patch.gz
>> 2014-08-09 616.4 kB 
>> I see this listing[1]  [sorted by date] in
>> http://www.spinics.net/lists/reiserfs-devel/maillist.html
>> Thanks Glenn
> 
> The patches marked with [RFC] are pre-experimental, that is, "request
for
> comments". They are not to be applied to any configuration with
significant
> data, not to mention in any way production systems.
> 
> Remaining ones are a bit less experimental, but anyway -- they are still
> up to
> review. Testing is appreciated, but... it can result in anything.
> 
> Currently there are three actual patchsets "in flight":
> 
> - [RFC] [PATCHv3 0/9] reiser4: batch discard support (FITRIM ioctl):
> initial implementation.
> - [PATCH 0/2] reiser4: block deallocation fixes.
> - [PATCH 0/3] reiser4: space grabbing fixes.
> 
> The main discard support patchset,
> 
> - [PATCHv7 0/6] reiser4: discard support: simplified and race-free
initial
> implementation.
> 
> is already reviewed by Edward and uploaded to sourceforge under name of
> 3.15.1-reiser4-basic-discard-support.patch.gz. It is to be applied on
top
> of
> reiser4-for-3.15.1.
> 
> The "in-flight" patchsets are to be applied on top of discard support
> patch.
> 
> Hope that helps,

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.

Cheers Glenn

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[Ivan Shapovalov]

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

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,
-- 
Ivan Shapovalov / intelfx /

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[doiggl]

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.

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

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[Edward Shishkin]

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

Re: Which patches can be applied on top of reiser4-for-3.15.1.patch.gz

[doiggl]

> 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.
> 
Hello,
Thanks for the information.
I'll wait for the new revisions.
Thank you 
Cheers Glenn.