From: Jens Axboe <axboe@kernel.dk>
To: "Lamkin, Eric" <Eric.Lamkin@lsi.com>, David Nellans <david@nellans.org>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio replay
Date: Wed, 26 Feb 2014 09:49:39 -0800 [thread overview]
Message-ID: <530E2933.2080903@kernel.dk> (raw)
In-Reply-To: <934f861a97f2443aa35296c2d6d8c848@BN1PR07MB437.namprd07.prod.outlook.com>
On 2014-02-26 06:23, Lamkin, Eric wrote:
> David,
>
> Thanks for responding.
> I sent the below out last week but didn't get a reply so thought I'd try a simpler 'what works' tactic this morning.
> As seen in the below I'm using 2.0.10.
I just ran a quick test here, current -git seems to work fine for me. It
might be a bit finicky in that the error handling isn't stellar, which
I'm thinking could be your issue since you have dropped events in your
blktraces. You need to eliminate any dropped events - either log to
tmpfs or send the traces over the network, that would likely do it.
If that doesn't solve it for you, please boil this down to a smaller
test case. Start with one device. Does that work? Up the complexity
until you see an issue, then I can likely help you get this fixed if I
get the problematic trace.
--
Jens Axboe
next prev parent reply other threads:[~2014-02-26 17:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:44 fio replay Lamkin, Eric
2014-02-26 14:13 ` David Nellans
2014-02-26 14:23 ` Lamkin, Eric
2014-02-26 15:30 ` Sitsofe Wheeler
2014-02-26 15:48 ` Lamkin, Eric
2014-02-26 16:15 ` Sitsofe Wheeler
2014-02-26 17:49 ` Jens Axboe [this message]
2014-02-26 21:44 ` Jens Axboe
2014-02-26 21:55 ` Lamkin, Eric
2014-02-27 18:48 ` Jens Axboe
2014-02-27 20:12 ` Lamkin, Eric
2014-03-03 13:25 ` Lamkin, Eric
2014-03-04 3:12 ` Alireza Haghdoost
2014-03-04 13:37 ` Lamkin, Eric
2014-03-06 15:55 ` Jens Axboe
2014-03-06 16:12 ` Lamkin, Eric
2014-03-28 13:52 ` Lamkin, Eric
2014-04-10 15:37 ` Lamkin, Eric
-- strict thread matches above, loose matches on Subject: below --
2014-02-20 16:39 Lamkin, Eric
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=530E2933.2080903@kernel.dk \
--to=axboe@kernel.dk \
--cc=Eric.Lamkin@lsi.com \
--cc=david@nellans.org \
--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 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.