All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Liao Yuanhong <liaoyuanhong@vivo.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org, bo.wu@vivo.com,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5] f2fs:Add write priority option based on zone UFS
Date: Mon, 05 Aug 2024 23:30:51 +0000	[thread overview]
Message-ID: <172290065174.2803.15142106569963496847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240715123451.7918-1-liaoyuanhong@vivo.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 15 Jul 2024 20:34:51 +0800 you wrote:
> Currently, we are using a mix of traditional UFS and zone UFS to support
> some functionalities that cannot be achieved on zone UFS alone. However,
> there are some issues with this approach. There exists a significant
> performance difference between traditional UFS and zone UFS. Under normal
> usage, we prioritize writes to zone UFS. However, in critical conditions
> (such as when the entire UFS is almost full), we cannot determine whether
> data will be written to traditional UFS or zone UFS. This can lead to
> significant performance fluctuations, which is not conducive to
> development and testing. To address this, we have added an option
> zlu_io_enable under sys with the following three modes:
> 1) zlu_io_enable == 0:Normal mode, prioritize writing to zone UFS;
> 2) zlu_io_enable == 1:Zone UFS only mode, only allow writing to zone UFS;
> 3) zlu_io_enable == 2:Traditional UFS priority mode, prioritize writing to
> traditional UFS.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v5] f2fs:Add write priority option based on zone UFS
    https://git.kernel.org/jaegeuk/f2fs/c/8444ce524947

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
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: patchwork-bot+f2fs@kernel.org
To: Liao Yuanhong <liaoyuanhong@vivo.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
	linux-kernel@vger.kernel.org, bo.wu@vivo.com,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v5] f2fs:Add write priority option based on zone UFS
Date: Mon, 05 Aug 2024 23:30:51 +0000	[thread overview]
Message-ID: <172290065174.2803.15142106569963496847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240715123451.7918-1-liaoyuanhong@vivo.com>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 15 Jul 2024 20:34:51 +0800 you wrote:
> Currently, we are using a mix of traditional UFS and zone UFS to support
> some functionalities that cannot be achieved on zone UFS alone. However,
> there are some issues with this approach. There exists a significant
> performance difference between traditional UFS and zone UFS. Under normal
> usage, we prioritize writes to zone UFS. However, in critical conditions
> (such as when the entire UFS is almost full), we cannot determine whether
> data will be written to traditional UFS or zone UFS. This can lead to
> significant performance fluctuations, which is not conducive to
> development and testing. To address this, we have added an option
> zlu_io_enable under sys with the following three modes:
> 1) zlu_io_enable == 0:Normal mode, prioritize writing to zone UFS;
> 2) zlu_io_enable == 1:Zone UFS only mode, only allow writing to zone UFS;
> 3) zlu_io_enable == 2:Traditional UFS priority mode, prioritize writing to
> traditional UFS.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v5] f2fs:Add write priority option based on zone UFS
    https://git.kernel.org/jaegeuk/f2fs/c/8444ce524947

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-08-05 23:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  6:29 [f2fs-dev] [PATCH] f2fs:Add write priority option based on zone UFS Liao Yuanhong via Linux-f2fs-devel
2024-07-02  6:29 ` Liao Yuanhong
2024-07-04  8:46 ` [f2fs-dev] " Chao Yu
2024-07-04  8:46   ` Chao Yu
2024-07-05  9:46 ` [f2fs-dev] [PATCH v2] " Liao Yuanhong via Linux-f2fs-devel
2024-07-05  9:46   ` Liao Yuanhong
2024-07-08  4:00   ` [f2fs-dev] " Chao Yu
2024-07-08  4:00     ` Chao Yu
2024-07-09  2:16 ` [f2fs-dev] [PATCH v3] " Liao Yuanhong via Linux-f2fs-devel
2024-07-09  2:16   ` Liao Yuanhong
2024-07-09  9:44   ` [f2fs-dev] " Chao Yu
2024-07-09  9:44     ` Chao Yu
2024-07-10  3:06 ` [f2fs-dev] [PATCH v4] " Liao Yuanhong via Linux-f2fs-devel
2024-07-10  3:06   ` Liao Yuanhong
2024-07-12  7:39   ` [f2fs-dev] " Chao Yu
2024-07-12  7:39     ` Chao Yu
2024-07-15 12:34 ` [f2fs-dev] [PATCH v5] " Liao Yuanhong via Linux-f2fs-devel
2024-07-15 12:34   ` Liao Yuanhong
2024-07-22  1:31   ` [f2fs-dev] " Chao Yu
2024-07-22  1:31     ` Chao Yu
2024-08-05 23:30   ` patchwork-bot+f2fs [this message]
2024-08-05 23:30     ` [f2fs-dev] " 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=172290065174.2803.15142106569963496847.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=bo.wu@vivo.com \
    --cc=jaegeuk@kernel.org \
    --cc=liaoyuanhong@vivo.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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.