From: Daejun Park <daejun7.park@samsung.com>
To: Bart Van Assche <bvanassche@acm.org>,
Daejun Park <daejun7.park@samsung.com>,
KANCHAN JOSHI <joshi.k@samsung.com>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
Niklas Cassel <Niklas.Cassel@wdc.com>,
Avri Altman <Avri.Altman@wdc.com>, Bean Huo <huobean@gmail.com>,
Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Seonghun Kim <seonghun-sui.kim@samsung.com>,
Jorn Lee <lunar.lee@samsung.com>,
Sung-Jun Park <sungjun07.park@samsung.com>,
Hyunji Jeon <hyunji.jeon@samsung.com>,
Dongwoo Kim <dongwoo7565.kim@samsung.com>,
Seongcheol Hong <sc01.hong@samsung.com>,
Jaeheon Lee <jaeheon7.lee@samsung.com>,
Wonjong Song <wj3.song@samsung.com>,
JinHwan Park <jh.i.park@samsung.com>,
Yonggil Song <yonggil.song@samsung.com>,
Soonyoung Kim <overmars.kim@samsung.com>,
Shinwoo Park <sw_kr.park@samsung.com>,
Seokhwan Kim <sukka.kim@samsung.com>
Subject: RE:(2) (2) [PATCH v3 01/14] fs: Move enum rw_hint into a new header file
Date: Thu, 02 Nov 2023 16:31:55 +0900 [thread overview]
Message-ID: <20231102073155epcms2p3d1e288b7b81e213fbb32ecc0cc48e094@epcms2p3> (raw)
In-Reply-To: <c06b2624-b05b-48d4-840d-beb208aa33dc@acm.org>
Hi Bart,
>On 10/31/23 23:39, Daejun Park wrote:
>>> On 10/30/23 04:11, Kanchan Joshi wrote:
>>>> On 10/18/2023 2:17 AM, Bart Van Assche wrote:
>>> Thanks for having taken a look at this patch series. Jens asked for data
>>> that shows that this patch series improves performance. Is this
>>> something Samsung can help with?
>>
>> We analyzed the NAND block erase counter with and without stream separation
>> through a long-term workload in F2FS.
>> The analysis showed that the erase counter is reduced by approximately 40%
>> with stream seperation.
>> Long-term workload is a scenario where erase and write are repeated by
>> stream after performing precondition fill for each temperature of F2FS.
>
>Hi Daejun,
>
>Thank you for having shared this data. This is very helpful. Since I'm
>not familiar with the erase counter: does the above data perhaps mean
>that write amplification is reduced by 40% in the workload that has been
>examined?
WAF is not only caused by GC. It is also caused by other reasons.
During device GC, the valid pages in the victim block are migrated, and a
lower erase counter means that the effective GC is performed by selecting
a victim block with a small number of invalid pages.
Thus, it can be said that the WAF can be decreased about 40% by selecting
fewer victim blocks during device GC.
Thanks,
Daejun
>
>Thanks,
>
>Bart.
next prev parent reply other threads:[~2023-11-02 7:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:47 [PATCH v3 00/14] Pass data temperature information to SCSI disk devices Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 01/14] fs: Move enum rw_hint into a new header file Bart Van Assche
2023-10-30 11:11 ` Kanchan Joshi
2023-10-30 16:10 ` Bart Van Assche
[not found] ` <CGME20231017204823epcas5p2798d17757d381aaf7ad4dd235f3f0da3@epcms2p1>
2023-11-01 6:39 ` Daejun Park
2023-11-01 16:45 ` (2) " Bart Van Assche
[not found] ` <CGME20231017204823epcas5p2798d17757d381aaf7ad4dd235f3f0da3@epcms2p3>
2023-11-02 7:31 ` Daejun Park [this message]
2023-10-17 20:47 ` [PATCH v3 02/14] block: Restore data lifetime support in struct bio and struct request Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 03/14] fs: Restore write hint support Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 04/14] fs/f2fs: Restore data lifetime support Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 05/14] scsi: core: Query the Block Limits Extension VPD page Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 06/14] scsi_proto: Add structures and constants related to I/O groups and streams Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 07/14] sd: Translate data lifetime information Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 08/14] scsi_debug: Reduce code duplication Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 09/14] scsi_debug: Support the block limits extension VPD page Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 10/14] scsi_debug: Rework page code error handling Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 11/14] scsi_debug: Rework subpage " Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 12/14] scsi_debug: Implement the IO Advice Hints Grouping mode page Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 13/14] scsi_debug: Implement GET STREAM STATUS Bart Van Assche
2023-10-17 20:47 ` [PATCH v3 14/14] scsi_debug: Maintain write statistics per group number Bart Van Assche
2023-10-18 19:09 ` [PATCH v3 00/14] Pass data temperature information to SCSI disk devices Jens Axboe
2023-10-18 19:34 ` Bart Van Assche
2023-10-19 0:33 ` Damien Le Moal
2023-10-19 16:48 ` Bart Van Assche
2023-10-19 22:40 ` Damien Le Moal
2023-10-19 23:00 ` Damien Le Moal
2023-10-20 20:45 ` Bart Van Assche
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=20231102073155epcms2p3d1e288b7b81e213fbb32ecc0cc48e094@epcms2p3 \
--to=daejun7.park@samsung.com \
--cc=Avri.Altman@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=bvanassche@acm.org \
--cc=chao@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dongwoo7565.kim@samsung.com \
--cc=hch@lst.de \
--cc=huobean@gmail.com \
--cc=hyunji.jeon@samsung.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jaeheon7.lee@samsung.com \
--cc=jh.i.park@samsung.com \
--cc=jlayton@kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lunar.lee@samsung.com \
--cc=martin.petersen@oracle.com \
--cc=overmars.kim@samsung.com \
--cc=sc01.hong@samsung.com \
--cc=seonghun-sui.kim@samsung.com \
--cc=sukka.kim@samsung.com \
--cc=sungjun07.park@samsung.com \
--cc=sw_kr.park@samsung.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wj3.song@samsung.com \
--cc=yonggil.song@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).