From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: hongyu.jin@unisoc.com, ke.wang@unisoc.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH V3] f2fs: add REQ_TIME time update for some user behaviors
Date: Wed, 20 Mar 2024 17:33:48 +0800 [thread overview]
Message-ID: <ee24b313-a168-471e-b60f-1404c69e61a7@kernel.org> (raw)
In-Reply-To: <1710915736-31823-1-git-send-email-zhiguo.niu@unisoc.com>
On 2024/3/20 14:22, Zhiguo Niu wrote:
> some user behaviors requested filesystem operations, which
> will cause filesystem not idle.
> Meanwhile adjust some f2fs_update_time(REQ_TIME) positions.
>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
ke.wang@unisoc.com, hongyu.jin@unisoc.com
Subject: Re: [PATCH V3] f2fs: add REQ_TIME time update for some user behaviors
Date: Wed, 20 Mar 2024 17:33:48 +0800 [thread overview]
Message-ID: <ee24b313-a168-471e-b60f-1404c69e61a7@kernel.org> (raw)
In-Reply-To: <1710915736-31823-1-git-send-email-zhiguo.niu@unisoc.com>
On 2024/3/20 14:22, Zhiguo Niu wrote:
> some user behaviors requested filesystem operations, which
> will cause filesystem not idle.
> Meanwhile adjust some f2fs_update_time(REQ_TIME) positions.
>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-03-20 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 6:22 [f2fs-dev] [PATCH V3] f2fs: add REQ_TIME time update for some user behaviors Zhiguo Niu
2024-03-20 6:22 ` Zhiguo Niu
2024-03-20 9:33 ` Chao Yu [this message]
2024-03-20 9:33 ` Chao Yu
2024-04-10 7:19 ` [f2fs-dev] " Zhiguo Niu
2024-04-10 7:19 ` Zhiguo Niu
2024-04-12 20:53 ` [f2fs-dev] " Jaegeuk Kim
2024-04-12 20:53 ` Jaegeuk Kim
2024-04-14 15:32 ` [f2fs-dev] " patchwork-bot+f2fs
2024-04-14 15:32 ` patchwork-bot+f2fs
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=ee24b313-a168-471e-b60f-1404c69e61a7@kernel.org \
--to=chao@kernel.org \
--cc=hongyu.jin@unisoc.com \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhiguo.niu@unisoc.com \
/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.