From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Sahitya Tummala <stummala@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: allow to change discard policy based on cached discard cmds
Date: Thu, 25 Mar 2021 18:21:42 -0700 [thread overview]
Message-ID: <YF03JuWi9bYL11e6@google.com> (raw)
In-Reply-To: <20210326011756.GE8562@codeaurora.org>
On 03/26, Sahitya Tummala wrote:
> 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.
Ha, need more coffee. Thanks for pointing it out. :)
>
> 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@codeaurora.org>
> >
> > Reviewed-by: Chao Yu <yuchao0@huawei.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.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Sahitya Tummala <stummala@codeaurora.org>
Cc: Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] f2fs: allow to change discard policy based on cached discard cmds
Date: Thu, 25 Mar 2021 18:21:42 -0700 [thread overview]
Message-ID: <YF03JuWi9bYL11e6@google.com> (raw)
In-Reply-To: <20210326011756.GE8562@codeaurora.org>
On 03/26, Sahitya Tummala wrote:
> 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.
Ha, need more coffee. Thanks for pointing it out. :)
>
> 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@codeaurora.org>
> >
> > Reviewed-by: Chao Yu <yuchao0@huawei.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.
next prev parent reply other threads:[~2021-03-26 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9:29 [f2fs-dev] [PATCH v3] f2fs: allow to change discard policy based on cached discard cmds Sahitya Tummala
2021-03-16 9:29 ` Sahitya Tummala
2021-03-16 11:08 ` [f2fs-dev] " Chao Yu
2021-03-16 11:08 ` Chao Yu
2021-03-26 1:17 ` [f2fs-dev] " Sahitya Tummala
2021-03-26 1:17 ` Sahitya Tummala
2021-03-26 1:21 ` Jaegeuk Kim [this message]
2021-03-26 1:21 ` Jaegeuk Kim
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=YF03JuWi9bYL11e6@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.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.