From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EF94D610C for ; Mon, 22 Jul 2024 01:31:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721611866; cv=none; b=oVMixx1qjj2vdhgD9qulZizwjFy/fnXdHeM7hCbNJ1fFaVVJ45a9y095UEeukOvWYxH1r0oCba6qXYKEuxZPrQ5f/mhMoRBn67TgGFn3G1puaYueeU/KM5lmPo1BQ1FhMO+/5/QasQN0Ud5PA6V0uIg30Tf66vXUba6AmkdKOWA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721611866; c=relaxed/simple; bh=Pgdfoi+plDo5Sv3bTklJaLHXbBK8ZHhX9xR+sbaiMhQ=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=lE7yluMSuc4TueUm1osv0IIeY5o54++usZX22lc2p7h9T5h0BvvomWMl4ngme/s2O9ifxwnC65mPTkkccg8VmmkLU0dj4UCj9QBkGO7BAoJStyYPfUIOfVxiRrGNzZWrfqs69JaxImtBgwhUevllTOl2dnDy5EhJCWHWnQGghtE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hkOOIsmv; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hkOOIsmv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 71E7AC116B1; Mon, 22 Jul 2024 01:31:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1721611865; bh=Pgdfoi+plDo5Sv3bTklJaLHXbBK8ZHhX9xR+sbaiMhQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=hkOOIsmvpuHAylM3fafNyX9Gn3LhzrBn8erzTFGQ9ZBy02HJXjLFkpkI1EUkGuBV2 aYBm2YapcZDduVx8+HlYNUy6jF/cZ+vpG5qveZroDz55Gidx+7llkY3ubUhYMWL2zH pV7TFFM0fUNGKXmcoCJjx15/ClYikEIEVm0sHs/KaFxI28g7KHjHjbUmmtBQyewuyQ 3JwMMua7ECXOkI4s6LMJcsOrx2lOMFnnpyso6FnNc76/Y/YJM/zEQIgti7vHk51/dG j2Kun6/jsqdtrs7heEi1nCDgdO90dKMEdOcvBt1LICZPonsz1Rb7fRvtUo0MtCXtHc m74JMPb3appVw== Message-ID: Date: Mon, 22 Jul 2024 09:31:01 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v5] f2fs:Add write priority option based on zone UFS To: Liao Yuanhong , Jaegeuk Kim Cc: bo.wu@vivo.com, linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org References: <20240702062952.28859-1-liaoyuanhong@vivo.com> <20240715123451.7918-1-liaoyuanhong@vivo.com> Content-Language: en-US From: Chao Yu In-Reply-To: <20240715123451.7918-1-liaoyuanhong@vivo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2024/7/15 20:34, Liao Yuanhong 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. > > Signed-off-by: Liao Yuanhong > Signed-off-by: Wu Bo Reviewed-by: Chao Yu Thanks,