From: Jens Axboe <jaxboe@fusionio.com>
To: Chuck Tuffli <ctuffli@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: using ioengine=sg
Date: Fri, 27 Aug 2010 18:56:02 +0200 [thread overview]
Message-ID: <4C77EE22.6020009@fusionio.com> (raw)
In-Reply-To: <AANLkTikN0M5eVXOAi9APqeS2Q7tiuYPacMsWiO0FnAWC@mail.gmail.com>
On 2010-08-27 17:40, Chuck Tuffli wrote:
> On Fri, Aug 27, 2010 at 12:03 AM, Jens Axboe <jaxboe@fusionio.com> wrote:
> ...
>> You are not doing anything wrong, it's a bug. This patch will fix
>> it.
>
> Thanks for the patch. Now I see the following
>
>> sudo ./fio sgtest.fio
> /dev/sg2: (g=0): rw=read, bs=512-512/512-512, ioengine=sg, iodepth=1
> Starting 1 process
> Jobs: 1 (f=0): [R] [12900.0% done] [0K/0K /s] [0/0 iops] [eta
> 1158050441d:06h:58m:08s]
Works for me, exact same job file. Can you do an sg_inq /dev/sg2?
--
Jens Axboe
next prev parent reply other threads:[~2010-08-27 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 19:25 using ioengine=sg Chuck Tuffli
2010-08-27 7:03 ` Jens Axboe
2010-08-27 15:40 ` Chuck Tuffli
2010-08-27 16:56 ` Jens Axboe [this message]
2010-08-27 21:37 ` Chuck Tuffli
2010-08-28 6:53 ` 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=4C77EE22.6020009@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=ctuffli@gmail.com \
--cc=fio@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox