From: Jens Axboe <jens.axboe@oracle.com>
To: Radha Ramachandran <radha@google.com>
Cc: fio@vger.kernel.org
Subject: Re: Patch to write patterns > 4 bytes
Date: Tue, 27 Oct 2009 08:55:16 +0100 [thread overview]
Message-ID: <20091027075516.GR10727@kernel.dk> (raw)
In-Reply-To: <66dfd3fe0910261710n62740f75y6946ebd00b2f9ab6@mail.gmail.com>
On Mon, Oct 26 2009, Radha Ramachandran wrote:
> Hi,
> This is the patch I have to write/read/verify hex patterns of size > 4 bytes.
> I have tested these on hard drives and did not see any performance
> change. Iam assuming the performance drop if any might show up in the
> read phase for probably solid state drives and maybe it can be worked
> around using the asynchronous verify flag.
Unfortunately, this patch is white space damaged so doesn't apply.
Perhaps send it as an attachment instead? And for extra brownie points,
updating the fio.1 man page as well would be good :-)
--
Jens Axboe
next prev parent reply other threads:[~2009-10-27 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 0:10 Patch to write patterns > 4 bytes Radha Ramachandran
2009-10-27 7:55 ` Jens Axboe [this message]
2009-10-27 18:19 ` Radha Ramachandran
2009-10-27 19:15 ` Jens Axboe
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=20091027075516.GR10727@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fio@vger.kernel.org \
--cc=radha@google.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