Re: [RESEND][PATCH 0/3 BUG,RFC] release block-device-mapping buffer_heads which have the filesystem private data for avoiding oom-killer

[Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>]

Ted-san,
Thanks for your applying.

Theodore Tso wrote:
> Okajima-san,
> 
> I've added your patches to the ext4 patch queue for testing.  I did
> make some changes to the commit descriptions for clarity's sake
> 
> -------------------------
> vfs: add releasepages hooks to block devices which can be used by file systems
<SNIP>
> -------------------------
> ext3: provide function to release journal heads under memory pressure
<SNIP>
> -------------------------
> ext4: implement release_metadata to release private data under memory pressure
<SNIP>
> ----------------------
> 
> Also, in the 2nd and 3rd patches, I made change to the comment
> describing ext[34]_release_metadata.  It now reads:
> 
> /*
>  * Try to release metadata pages (indirect blocks, directories) which are
>  * mapped via the block device.  Since these pages could have journal heads
>  * which would prevent try_to_free_buffers() from freeing them, we must use
>  * jbd[2] layer's try_to_free_buffers() function to release them.
>  */
> 
> I hope you agree these changes are more descriptive of what is going
> on in the patch.
OK!

I agree to your all appropriate changes.

(I am looking forward to merging them to mainstream kernel early. :-))

Best regards,
Toshiyuki Okajima