lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 25 Oct 2007 19:45:44 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	"Jose R. Santos" <jrs@...ibm.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: compilebench numbers for ext4

On Thu, 25 Oct 2007 17:40:25 -0500
"Jose R. Santos" <jrs@...ibm.com> wrote:

> > > 
> > > I really want to use seekwatcher to test some of the stuff that
> > > I'm doing for flex_bg feature but it barfs on me in my test
> > > machine.
> > > 
> > > running :sleep 10:
> > > done running sleep 10
> > > Device: /dev/sdh
> > >   Total:                     0 events (dropped 0),     1368 KiB
> > > data blktrace done
> > > Traceback (most recent call last):
> > >   File "/usr/bin/seekwatcher", line 534, in ?
> > >     add_range(hist, step, start, size)
> > >   File "/usr/bin/seekwatcher", line 522, in add_range
> > >     val = hist[slot]
> > > IndexError: list index out of range
> > 
> > I don't think you have any events in the trace.  Try this instead:
> > 
> > echo 3 > /proc/sys/vm/drop_caches
> > seekwatcher -t find-trace -d /dev/xxxx -p 'find /usr/local -type f'
> 
> Nope, get the same error.  There does seem to be data recorded in the
> trace files and iostat does show activity on the disk.

Hmmm, could you please send me your trace files.  There will be one for
each cpu, starting with find-trace-blktrace

> > I wanted to benchmark flexbg too, but couldn't quite figure out the
> > correct patch combination ;)
> 
> Ill attach e2progfs and Kernel patches but do realize that these are
> experimental patches that Im using to test what layout would work
> best.  Don't take them too seriously as it is largely incomplete.

Thanks, I'll try this out.

> 
> Currently trying to come up with workloads to test this and other
> changes with.  Im am warming up to yours :)

At least for the write phases of compilebench, it should benefit from
data and metadata separation.  It made a very big difference in btrfs,
(from 20MB/s up to 32MB/s on create).  However it did make the read
phases slower.

-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists