iozone patch to allow for larger tests

As noted a few times here, iozone as written, has numerous hard-wired quantities within it, some of which impede testing for large and fast systems. Here is a simple patch to fix one of the issues …

diff -uNr iozone3_283/src/current/iozone.c iozone3_283.new/src/current/iozone.c --- iozone3_283/src/current/iozone.c 2007-02-19 12:12:18.000000000 -0500 +++ iozone3_283.new/src/current/iozone.c 2007-09-12 11:47:19.000000000 -0400 @@ -741,7 +741,7 @@ /* At 16 Meg switch to large records */ #define CROSSOVER (16*1024) /* Maximum buffer size*/ -#define MAXBUFFERSIZE (16*1024*1024) +#define MAXBUFFERSIZE (1024*1024*1024) #endif /* Maximum number of children. Threads/procs/clients */ Smaller buffers don’t help when you need to do really huge IO’s (streaming of GB of data). Sadly, as this is a 32 bit code (lots of ints and assumed size) we can’t create really huge in-ram buffers. Since our customers are talking about working with 100’s of GB on a regular basis, we need big huge buffers.