Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Wolford,
	Jeff (HP Servers - Web Scale performance)" <jeff.wolford@hpe.com>,
	"Benchmark FIO (fio@vger.kernel.org)" <fio@vger.kernel.org>
Subject: Re: FIO: adding SMR ZONE management commands
Date: Wed, 21 Oct 2015 14:57:15 -0600	[thread overview]
Message-ID: <5627FC2B.2@kernel.dk> (raw)
In-Reply-To: <DC12A894E6E89949B50B1F35C3903C1B3B2B0ECA@G9W0747.americas.hpqcorp.net>

On 10/20/2015 02:30 PM, Wolford, Jeff (HP Servers - Web Scale 
performance) wrote:
> Has any consideration been given to adding support for SMR Management ZONE commands to FIO (obviously in block mode) ?
> (Open, Close, Report, Finish, Reset Write Pointer) ?

Some folks from Seagate expressed interest and desire for working on SMR 
for fio this summer, not sure if anything came of that yet. I'll check 
with them. Personally I haven't looked at it much, I don't even have any 
SMR hw.

-- 
Jens Axboe



      reply	other threads:[~2015-10-21 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 20:30 FIO: adding SMR ZONE management commands Wolford, Jeff (HP Servers - Web Scale performance)
2015-10-21 20:57 ` Jens Axboe [this message]

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=5627FC2B.2@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jeff.wolford@hpe.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