From: Jens Axboe <axboe@kernel.dk>
To: Dan Ehrenberg <dehrenberg@chromium.org>, fio@vger.kernel.org
Cc: gwendal@chromium.org
Subject: Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
Date: Tue, 14 Apr 2015 18:43:32 -0600 [thread overview]
Message-ID: <552DB434.2060709@kernel.dk> (raw)
In-Reply-To: <1429052300-9822-3-git-send-email-dehrenberg@chromium.org>
On 04/14/2015 04:58 PM, Dan Ehrenberg wrote:
> In this new mode, sequential trims and writes are interspersed by first
> doing a trim at a particular offset, then doing writes starting from
> that offset until the start of the next trim block, then another trim,
> etc. This workload is designed to match the requirements of NAND flash,
> if trims are implemented as erases.
At first I found this a little confusing, but now I get it. It's a bit
different to what other mixed workloads would be. Perhaps rename it to
'trimwrite'? Also needs adding to the man page and HOWTO.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-15 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 22:58 [PATCH 0/7] Framework for NAND lifetime testing Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 1/7] Allow trim on any file type Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Dan Ehrenberg
2015-04-15 0:43 ` Jens Axboe [this message]
2015-04-15 17:49 ` Daniel Ehrenberg
2015-04-15 19:30 ` Jens Axboe
2015-04-15 20:28 ` Daniel Ehrenberg
2015-04-15 21:02 ` Jens Axboe
2015-04-14 22:58 ` [PATCH 3/7] Collect a block-wise histogram of trim and write errors Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 4/7] mtd: Add CONFIG_MTD to ./configure script Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 5/7] mtd: Import libmtd with modifications to make it compile Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 6/7] mtd: ioengine Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 7/7] mtd: example job file Dan Ehrenberg
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=552DB434.2060709@kernel.dk \
--to=axboe@kernel.dk \
--cc=dehrenberg@chromium.org \
--cc=fio@vger.kernel.org \
--cc=gwendal@chromium.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.