Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Michael O'Sullivan <michael.osullivan@auckland.ac.nz>
Cc: fio@vger.kernel.org, "Daniel, Steve" <Steve.Daniel@netapp.com>,
	Glen Ogilvie <gogilvie@oss.co.nz>
Subject: Re: Integrate SPC-1 with fio, version 2 ready for options
Date: Wed, 10 Feb 2010 11:08:17 +0100	[thread overview]
Message-ID: <20100210100817.GC1025@kernel.dk> (raw)
In-Reply-To: <4B72792C.5030709@auckland.ac.nz>

On Wed, Feb 10 2010, Michael O'Sullivan wrote:
> Hi everyone,
>
> Sorry for 2 posts in one day. I have edited my code since the last post  
> to make it easy to add options once I get some direction about using the  
> options and creating a parameter file. I have attached the patch. All  
> the configurable options are now set in set_spc1_options, which can be  
> modified to read a parameter file.

Never apologize for posting too often! :-)

This is very interesting, I'll take a gander at it soonish, I'd like to
get SPC-1 integrated. Some quick thoughts before I get a closer look:

- Fio has the --profile switch, which was meant for things like this.
  It's not very expanded yet, but it could be. I think that is the way
  to go. Then you probably want to add some --profile=foo specific
  options, for setting options that only apply to that profile type.
  That would be SPC-1 specific options.

- It would be a lot nicer if the IO generator was integrated, so you
  would not have to go through the iolog to store and retrieve work
  items.

-- 
Jens Axboe


  reply	other threads:[~2010-02-10 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10  9:15 Integrate SPC-1 with fio, version 2 ready for options Michael O'Sullivan
2010-02-10 10:08 ` Jens Axboe [this message]
2010-02-15 10:47 ` fio doesn't seem to generate IO Michael O'Sullivan
2010-02-23  9:20   ` 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=20100210100817.GC1025@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=Steve.Daniel@netapp.com \
    --cc=fio@vger.kernel.org \
    --cc=gogilvie@oss.co.nz \
    --cc=michael.osullivan@auckland.ac.nz \
    /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