All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Chris Worley <worleys@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Solaris issues in 1.3.1
Date: Wed, 5 Aug 2009 21:02:49 +0200	[thread overview]
Message-ID: <20090805190249.GD12579@kernel.dk> (raw)
In-Reply-To: <20090805185527.GB12579@kernel.dk>

On Wed, Aug 05 2009, Jens Axboe wrote:
> On Wed, Aug 05 2009, Chris Worley wrote:
> > I'm running fio 1.3.1 in Solaris.� I'm seeing two issues:
> > 
> > 1) Direct I/O throws an error.
> > 2) Performance is way too high.
> > 
> > W/o Direct I/O my size is set to 2.5x memory capacity to assure no
> > caching... yet performance for read/write is up to >7x the theoretical
> > speed of the storage device (i.e. it's reporting 7GB/s, when
> > theoretical for the device is 1GB/s).
> > 
> > I'm not seeing the reporting issue in 1.2.1.
> 
> Are you familiar with git? If yes, then you could try and bisect the
> issue. You would do something ala:
> 
> $ git bisect start
> $ git bisect good fio-1.21
> $ git bisect bad fio-1.31
> 
> and then git would checkout a point in between. You would then compile
> and run, checking if it works or not. If the version works, then you
> would reply with
> 
> $ git bisect good
> 
> if not, then you would do
> 
> $ git bisect bad
> 
> This continues until git tells you which commit is the defective one.
> I'll give it a spin on Solaris too, I recently put Solaris 11 on a box
> for test purposes.

Oh, and if you are not, just wait and I'll double check things here. But
please send me your job file(s) so I can reproduce more easily, thanks.

-- 
Jens Axboe


  reply	other threads:[~2009-08-05 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 18:10 Solaris issues in 1.3.1 Chris Worley
2009-08-05 18:55 ` Jens Axboe
2009-08-05 19:02   ` Jens Axboe [this message]
2009-08-05 19:18     ` Chris Worley

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=20090805190249.GD12579@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fio@vger.kernel.org \
    --cc=worleys@gmail.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 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.