From: Vincent Fu <vincentfu@gmail.com>
To: Adam Horshack <horshack@live.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: blog post on fio write zeroes performance
Date: Tue, 5 Nov 2024 15:36:59 -0500 [thread overview]
Message-ID: <422c7d4a-5b9b-48d5-adf7-355947d18014@gmail.com> (raw)
In-Reply-To: <PH7PR14MB74195A055EE5BF97F7054A32A4522@PH7PR14MB7419.namprd14.prod.outlook.com>
On 11/5/24 15:02, Adam Horshack wrote:
> Nice writeup Vincent. It's been a while since I've looked at the NVMe spec so perhaps I'm asking the wrong question but why is fio managing a data buffer for its handling of the Write Zero command? I would've assumed there's no data payload associated with that NVMe command, thus nothing that should even be subject to internal buffer scrambling inside fio.
>
> Regards,
>
> Adam
>
>
> ________________________________________
> From: Vincent Fu <vincentfu@gmail.com>
> Sent: Tuesday, November 5, 2024 2:41 PM
> To: fio@vger.kernel.org
> Cc: gost.dev@samsung.com
> Subject: blog post on fio write zeroes performance
>
> I am pleased to share a blog post about fio write zeroes performance:
>
> https://github.com/vincentkfu/fio-blog/wiki/How-could-write-zeroes-performance-be-worse-at-higher-queue-depths
>
> Read about the unexpected performance issue we encountered. Feedback is
> welcome.
>
> Vincent
>
>
When we added write zeroes support for the io_uring_cmd ioengine it was
not on our mind that the default behavior for fio is to scramble
buffers. Basically these patches just changed the opcode from a regular
write to write zeroes.
You do have a good point that perhaps fio should be smart enough to
avoid touching the buffers when doing write zeroes.
Thanks for the feedback!
Vincent
next prev parent reply other threads:[~2024-11-05 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 19:41 blog post on fio write zeroes performance Vincent Fu
2024-11-05 20:02 ` Adam Horshack
2024-11-05 20:36 ` Vincent Fu [this message]
2024-11-05 20:45 ` Terekhov, Mikhail
2024-11-05 21:32 ` Vincent Fu
2024-11-05 21:58 ` Sitsofe Wheeler
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=422c7d4a-5b9b-48d5-adf7-355947d18014@gmail.com \
--to=vincentfu@gmail.com \
--cc=fio@vger.kernel.org \
--cc=horshack@live.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