Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: user/des/phybs
Commits on Jul 17, 2014
  1. @dag-erling

    autoconfuse

    dag-erling authored
Commits on Sep 27, 2011
  1. @dag-erling

    Lengthen the progress bar to cover the entire width of the numbers which

    dag-erling authored
    will replace it, change the indicator character from '|' to 'O', and
    increase the update frequency.
Commits on Sep 26, 2011
  1. @dag-erling
  2. @dag-erling

    Add a man page.

    dag-erling authored
  3. @dag-erling

    Make -r the default.

    dag-erling authored
    Change the default minsize to bsize so we can tell if the logical and
    physical block sizes are the same.
  4. @dag-erling
Commits on Sep 14, 2010
  1. @dag-erling

    Fix an overflow in the tps calculation.

    dag-erling authored
    Noticed by:	Pieter de Goeje
Commits on Aug 15, 2010
  1. @dag-erling

    Instead of a hardcoding the block size, ask the device; default to 512

    dag-erling authored
    bytes for regular files.  Adjust all other default values accordingly.
Commits on Aug 14, 2010
  1. @dag-erling
Commits on Aug 13, 2010
  1. @dag-erling
Commits on Aug 12, 2010
  1. @dag-erling
  2. @dag-erling
  3. @dag-erling

    braino: stdout, not stdin!

    dag-erling authored
  4. @dag-erling
  5. @dag-erling
Commits on Aug 10, 2010
  1. @dag-erling

    Increase MINSIZE; there isn't much point in doing 512-byte

    dag-erling authored
    transactions, as they will always be either perfectly aligned or
    short.
    
    Increase STEP to MAXSIZE * 4; having STEP equal to MAXSIZE means that
    the last round actually tests sequential reading / writing, which is
    not what we're after.
    
    Instead of testing all offsets from 0 to size, test 0 and power-of-two
    multiples of BSIZE, since we assume that the physical block size is a
    power-of-two multiple of BSIZE.
    
    This should both shorten the test's run time and improve the
    significance of its output.
  2. @dag-erling
  3. @dag-erling

    This is a small program that runs a series of performance tests

    dag-erling authored
    designed to reveal the physical block size of a disk.  It performs a
    series of staggered reads and / or writes of different lengths at
    different alignments.  The idea is that a disk that has a large
    physical blocksize but simulates a smaller one will perform poorly,
    due to read-modify-write, except when both the I/O size and the offset
    are multiples of the physical block size.
    
    The program supports read-only, write-only and read-write tests.  The
    default is write-only.  A read-write test is probably not very useful,
    because it primes the cache in cases where the disk would actually
    perform an extra read.  A read-only test is useless except as a quick
    way to verify that the program works.
    
    Note that the program currently assumes a logical block size of 512
    bytes and that the parameters (size range, interval and iterations)
    are hardcoded.
Something went wrong with that request. Please try again.