linux-kernel - Re: [PATCH v3] f2fs: allow to change discard policy based on cached discard cmds

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 26 Mar 2021 06:47:56 +0530
From:   Sahitya Tummala <stummala@...eaurora.org>
To:     Chao Yu <yuchao0@...wei.com>, jaegeuk@...nel.org
Cc:     Jaegeuk Kim <jaegeuk@...nel.org>,
        linux-f2fs-devel@...ts.sourceforge.net,
        linux-kernel@...r.kernel.org, stummala@...eaurora.org
Subject: Re: [PATCH v3] f2fs: allow to change discard policy based on cached
 discard cmds

Hi Jaegeuk,

This latest v3 patch needs to be updated in f2fs tree.
The f2fs tree currently points to older version of patch.

Please make a note of it.

Thanks,
Sahitya.

On Tue, Mar 16, 2021 at 07:08:58PM +0800, Chao Yu wrote:
> On 2021/3/16 17:29, Sahitya Tummala wrote:
> >With the default DPOLICY_BG discard thread is ioaware, which prevents
> >the discard thread from issuing the discard commands. On low RAM setups,
> >it is observed that these discard commands in the cache are consuming
> >high memory. This patch aims to relax the memory pressure on the system
> >due to f2fs pending discard cmds by changing the policy to DPOLICY_FORCE
> >based on the nm_i->ram_thresh configured.
> >
> >Signed-off-by: Sahitya Tummala <stummala@...eaurora.org>
> 
> Reviewed-by: Chao Yu <yuchao0@...wei.com>
> 
> Thanks,

-- 
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.