[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0904031452290.7007@localhost.localdomain>
Date: Fri, 3 Apr 2009 15:06:29 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jeff Garzik <jeff@...zik.org>
cc: Chris Mason <chris.mason@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rees <drees76@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.29
On Fri, 3 Apr 2009, Jeff Garzik wrote:
>
> Since I am hacking on osdblk currently, I was too slack to code up a test.
> This is what bonnie++ says, at least...
Afaik, bonnie does it all in the page cache, and only tests random reads
(in the "random seek" test), not random writes.
> But I guess seeks are not very helpful on an SSD :) Any pre-built random
> write tests out there?
"fio" does well:
http://git.kernel.dk/?p=fio.git;a=summary
and I think it comes with a few example files. Here's the random write
file that Jens suggested, and that works pretty well..
It first creates a 2GB file to do the IO on, then does random 4k writes to
it with O_DIRECT.
If your SSD does badly at it, you'll just want to kill it, but it shows
you how many MB/s it's doing (or, in the sucky case, how many kB/s).
Linus
---
[global]
filename=testfile
size=2g
create_fsync=1
overwrite=1
[randwrites]
# make rw= 'randread' for random reads, 'read' for reads, etc
rw=randwrite
bs=4k
direct=1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists