From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Weird trim test results
Date: Thu, 25 Jul 2013 12:17:49 -0600 [thread overview]
Message-ID: <51F16BCD.1000202@kernel.dk> (raw)
In-Reply-To: <CAF+0mvnzF80RA8m2L9kZjrmT5OkuxYSwhGWOf+YXjOXv3RLCJA@mail.gmail.com>
Please don't top post...
On 07/25/2013 11:27 AM, Matthew Eaton wrote:
> Hi Jens,
>
> I'm running Ubuntu 12.04.2, my kernel is:
>
> Linux matt-work 3.5.0-36-generic #57~precise1-Ubuntu SMP Thu Jun 20
> 18:21:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> Here is the output I got from blktrace / blkparse:
>
> Total (sdb):
> Reads Queued: 166, 664KiB Writes Queued:
> 3001, 12004KiB
> Read Dispatches: 166, 664KiB Write Dispatches:
> 3001, 12004KiB
> Reads Requeued: 0 Writes Requeued: 0
> Reads Completed: 166, 664KiB Writes Completed:
> 3001, 1500KiB
> Read Merges: 0, 0KiB Write Merges:
> 0, 0KiB
> PC Reads Queued: 0, 0KiB PC Writes Queued:
> 0, 0KiB
> PC Read Disp.: 22, 3KiB PC Write Disp.:
> 0, 0KiB
> PC Reads Req.: 0 PC Writes Req.: 0
> PC Reads Compl.: 10 PC Writes Compl.: 0
> IO unplugs: 166 Timer unplugs: 0
That looks fine, it might just be coincidence that you are capped at
~100 IOPS. I don't think it's that unlikely that the this is the limit
for you, your device might have a fixed overhead associated with a trim
request. I'd have to look closer at your system to see if that's the
case or not.
--
Jens Axboe
next prev parent reply other threads:[~2013-07-25 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:22 Weird trim test results Matthew Eaton
2013-07-25 14:36 ` Jens Axboe
2013-07-25 17:27 ` Matthew Eaton
2013-07-25 18:17 ` Jens Axboe [this message]
2013-07-25 19:19 ` Matthew Eaton
2013-07-25 19:19 ` 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=51F16BCD.1000202@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=m.eaton82@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox