Flexible I/O Tester

• Thread Index

• RBD client cache
  • From: Jens Rosenboom <j.rosenboom@xxxxxxxx>
• [PATCH] Fix ETA calculations
  • From: Jens Rosenboom <j.rosenboom@xxxxxxxx>
• Issues with ETA calculations
  • From: Jens Rosenboom <j.rosenboom@xxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Job hangs on a NFS share with shared workload
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: Running a separate fio process for each disk?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Aggregate values in logs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Aggregate values in logs
  • From: GrAnt <626542@xxxxxxxxx>
• Re: Double output
  • From: GrAnt <626542@xxxxxxxxx>
• Re: relationship of fio versus gfio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: preliminary fio and gfio 2.2.10 Debian packages (UPDATE)
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: relationship of fio versus gfio
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: relationship of fio versus gfio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Double output
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Double output
  • From: GrAnt <626542@xxxxxxxxx>
• Re: Increasing startup time
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Increasing startup time
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Increasing startup time
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Fix spelling error in binary:
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Increasing startup time
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• relationship of fio versus gfio
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Increasing startup time
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Re: preliminary fio and gfio 2.2.10 Debian packages (UPDATE)
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• preliminary fio and gfio 2.2.10 Debian packages
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• [PATCH] Fix spelling error in binary:
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: Trying to understand a weird timeout when using fio and multipath IO
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: Trying to understand a weird timeout when using fio and multipath IO
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Trying to understand a weird timeout when using fio and multipath IO
  • From: Todd Lawall <tlawall@xxxxxxxxxxxxxxxxx>
• Re: FIO IO units block size setting function
  • From: vmokric <vojislav.mokric@xxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO IO units block size setting function
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO IO units block size setting function
  • From: vmokric <vojislav.mokric@xxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: DoubleDensity <doubledense@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Buttetsu Batou <doubledense@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Problem on using fio replay function with fio iolog trace
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Problem on using fio replay function with fio iolog trace
  • From: Hyukjoong Kim <wangmir@xxxxxxxxx>
• error on using fio trace replay
  • From: Hyukjoong Kim <wangmir@xxxxxxxxx>
• Re: FIO: adding SMR ZONE management commands
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO: adding SMR ZONE management commands
  • From: "Wolford, Jeff (HP Servers - Web Scale performance)" <jeff.wolford@xxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Threading vs forking
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO blocksize option clear out
  • From: vmokric <vojislav.mokric@xxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Threading vs forking
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Re: [PATCH] Fix Windows build by using lib/strcasestr.{c,h}
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: IO merge in engine
  • From: Fabrice Bacchella <fabrice.bacchella@xxxxxxxxx>
• [PATCH] Fix Windows build by using lib/strcasestr.{c,h}
  • From: Bruce Cran <bruce.cran@xxxxxxxxx>
• Re: IO merge in engine
  • From: Jens Axboe <axboe@xxxxxxxxx>
• IO merge in engine
  • From: Fabrice Bacchella <fabrice.bacchella@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/2] fio.1,HOWTO: keep 'iodepth_batch' option in sync
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 2/2] Introduce new option: iodepth_batch_complete_max
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [PATCH 1/2] fio.1,HOWTO: keep 'iodepth_batch' option in sync
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: Latency Output Question
  • From: Cheerio Cheerio <cheerios123@xxxxxxxxxxx>
• RE: Latency Output Question
  • From: Cheerio Cheerio <cheerios123@xxxxxxxxxxx>
• Re: Latency Output Question
  • From: Vincent Fu <Vincent.Fu@xxxxxxxxxxx>
• Re: Latency Output Question
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Latency Output Question
  • From: Jon Tango <cheerios123@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Ensure submission offload worker inherits parent's options
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Ensure submission offload worker inherits parent's options
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 2/2] verify: move meta header to generic verify_header
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [PATCH 1/2] fio.1: update description for 'buffer_pattern' and 'verify_pattern'
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• Re: [RFC 0/6] Add support of formats for the pattern input
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC 0/6] Add support of formats for the pattern input
  • From: Roman Peniaev <r.peniaev@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC 0/6] Add support of formats for the pattern input
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: failing to flush cache
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Wee nit in backend.c
  • From: Jens Axboe <axboe@xxxxxxxxx>
• failing to flush cache
  • From: Ken Raeburn <raeburn@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO Histogram - latency
  • From: neto from Brazil <Antonio.Jose.Rodrigues.Neto@xxxxxxxxxx>
• FIO Histogram - latency
  • From: neto from Brazil <Antonio.Jose.Rodrigues.Neto@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [RFC 6/6] use 'lib/pattern' to parse patterns and paste formats into buffers
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 5/6] add FIELD_SIZE macro to calculate the size of the specified field
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 4/6] verify: use 'cmp_pattern' from 'lib/pattern.c' to compare pattern and buffer
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 3/6] replace 'fill_pattern' with 'cpy_pattern' from 'lib/pattern.c'
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 2/6] lib/pattern: add set of functions to parse combined pattern input
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 1/6] lib/strntol: add 'strntol' function
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 0/6] Add support of formats for the pattern input
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• [RFC 0/6] Add support of formats for the pattern input
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: server mode and verify_dump
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: valgrind error "invalid read of size 4" in get_jobs_eta
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Clang static analyzer warnings
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] arch-ppc.h: Add ilog2 implementation for ppc64
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] arch-ppc.h: Add ilog2 implementation for ppc64
  • From: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Roman Peniaev <r.peniaev@xxxxxxxxx>
• Clang static analyzer warnings
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• server mode and verify_dump
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• valgrind error "invalid read of size 4" in get_jobs_eta
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Roman Peniaev <r.peniaev@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 1/1] verify: move meta header to generic verify_header
  • From: Roman Pen <r.peniaev@xxxxxxxxx>
• Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: Question about data integrity check
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Jens Axboe <axboe@xxxxxxxxx>
• PATCH: Don't lose pending completions on exit in time- or size-based job with asynchronous I/O engine
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: ask a question about fio
  • From: john gong <johngong0791@xxxxxxxxx>
• Re: Question about data integrity check
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: ask a question about fio
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: ask a question about fio
  • From: "danielabuggie ." <danielabuggie@xxxxxxxxx>
• Re: ask a question about fio
  • From: john gong <johngong0791@xxxxxxxxx>
• Re: ask a question about fio
  • From: "danielabuggie ." <danielabuggie@xxxxxxxxx>
• Re: ask a question about fio
  • From: john gong <johngong0791@xxxxxxxxx>
• Re: ask a question about fio
  • From: "danielabuggie ." <danielabuggie@xxxxxxxxx>
• Re: ask a question about fio
  • From: john gong <johngong0791@xxxxxxxxx>
• Re: ask a question about fio
  • From: "Kulkarni, Vasu" <vasu.kulkarni@xxxxxxxxx>
• Re: ask a question about fio
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• ask a question about fio
  • From: john gong <johngong0791@xxxxxxxxx>
• Re: Question about data integrity check
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Fwd: Question about data integrity check
  • From: Grant Grundler <grundler@xxxxxxxxxxxx>
• Logging starvation on large amount of threads
  • From: Gleb Stepanov <gstepanov@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Starvation on large amount of threads
  • From: Gleb Stepanov <glebstepanov1992@xxxxxxxxx>
• Re: gcc 5.1.1 and warnings when building fio on Linux with -flto
  • From: Jens Axboe <axboe@xxxxxxxxx>
• gcc 5.1.1 and warnings when building fio on Linux with -flto
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FreeBSD build broken following _Static_assert commit
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FreeBSD build broken following _Static_assert commit
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FreeBSD build broken following _Static_assert commit
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FreeBSD build broken following _Static_assert commit
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: Percentage/ETA progress indicator faulty with examples/tiobench-example.fio
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: Percentage/ETA progress indicator faulty with examples/tiobench-example.fio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FreeBSD build broken following _Static_assert commit
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: t/stest failures
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Question about data integrity check
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Percentage/ETA progress indicator faulty with examples/tiobench-example.fio
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: t/stest failures
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• t/stest failures
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• FreeBSD build broken following _Static_assert commit
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: competime_assert failure without -O3 optimization flag expected ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• competime_assert failure without -O3 optimization flag expected ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Fix testing and setting set_options bitmap
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] Fix testing and setting set_options bitmap
  • From: Akinobu Mita <akinobu.mita@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: query on verify_dump option
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Verify concentrated on first few drives
  • From: Gavin Martin <gavin.martin@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO creating empty latency log files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Verify concentrated on first few drives
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Verify concentrated on first few drives
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Verify concentrated on first few drives
  • From: Gavin Martin <gavin.martin@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [Suggestion] Aggregated Client/Server Stats Reporting
  • From: Ben England <bengland@xxxxxxxxxx>
• RE: what is the difference? start 2 fio instances and setting numjobs=2 ..
  • From: Carl Zwanzig <cpz@xxxxxxxxxxxxxxxxxx>
• what is the difference? start 2 fio instances and setting numjobs=2 ..
  • From: QB <viali.lee.mail@xxxxxxxxx>
• Re: [Suggestion] Aggregated Client/Server Stats Reporting
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Parameter Issue with 'ratemin'...
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [Suggestion] Aggregated Client/Server Stats Reporting
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• FIO creating empty latency log files
  • From: Reed Crowe <Reed.Crowe@xxxxxxxxxxx>
• Wired Latency Reporting in the FIO results
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• [Suggestion] Aggregated Client/Server Stats Reporting
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: Parameter Issue with 'ratemin'...
  • From: FIO-User-KKV <viali.lee@xxxxxxxxx>
• RE: Parameter Issue with 'ratemin'...
  • From: "Hinson, Roger" <Roger_Hinson@xxxxxxxxxx>
• Parameter Issue with 'ratemin'...
  • From: FIO-User-KKV <viali.lee@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Mixing command line and job file parameters
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: fio offset cycling.
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• fio offset cycling.
  • From: Adrin Fernandes <adrin.fernandes@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Michael Weinrich <micxer@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Urgent problem while using Fio to test random write performance
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: "danielabuggie ." <danielabuggie@xxxxxxxxx>
• Re: Urgent problem while using Fio to test random write performance
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: Urgent problem while using Fio to test random write performance
  • From: David Nellans <david@xxxxxxxxxxx>
• Urgent problem while using Fio to test random write performance
  • From: Nan WANG <wangnan@xxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Michael Weinrich <micxer@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Michael Weinrich <micxer@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Testing write master and multiple read clients on NFS share
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Brian Fulton <bfulton@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Testing write master and multiple read clients on NFS share
  • From: Michael Weinrich <micxer@xxxxxxxxx>
• Re: --thinktime seems not work
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: --thinktime seems not work
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: --thinktime seems not work
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: --thinktime seems not work
  • From: Rodrigo Ribeiro Gomes <rodrigorigomes@xxxxxxxxx>
• Re: --thinktime seems not work
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: --thinktime seems not work
  • From: Rodrigo Ribeiro Gomes <rodrigorigomes@xxxxxxxxx>
• --thinktime seems not work
  • From: rodrigo@xxxxxxxxxxxxxxx
• Re: --thinktime seems not work
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Write Pattern and Verify in separate run instance ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• --thinktime seems not work
  • From: Rodrigo Ribeiro Gomes <rodrigorigomes@xxxxxxxxx>
• Re: Write Pattern and Verify in separate run instance ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Write Pattern and Verify in separate run instance ?
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Re: linux /dev and normal files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Write Pattern and Verify in separate run instance ?
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• RE: linux /dev and normal files
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: linux /dev and normal files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Why Seperate Log Files?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: Why Seperate Log Files?
  • From: Jon Tango <cheerios123@xxxxxxxxxxx>
• Re: Why Seperate Log Files?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Why Seperate Log Files?
  • From: Jon Tango <cheerios123@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• RE: achieving a workload to get specific unique duplicate blocks
  • From: "Ruvinsky, Konstantin" <Konstantin.Ruvinsky@xxxxxxx>
• RE: achieving a workload to get specific unique duplicate blocks
  • From: "Ruvinsky, Konstantin" <Konstantin.Ruvinsky@xxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Iuliu Rus <iuliur@xxxxxxxxxx>
• Re: [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• [PATCH] Add Windows ctime_r implementation and empty ioctl.h header
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Iuliu Rus <iuliur@xxxxxxxxxx>
• RE: FIO on ARM
  • From: Alexey Skidanov <Alexey.Skidanov@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO on ARM
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO on ARM
  • From: Alexey Skidanov <Alexey.Skidanov@xxxxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Brian Fulton <bfulton@xxxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Unexpected runtime when running FIO in time based
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Brian Fulton <bfulton@xxxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Brian Fulton <bfulton@xxxxxxxxxx>
• Re: [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: achieving a workload to get specific unique duplicate blocks
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Unexpected runtime when running FIO in time based
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Unexpected runtime when running FIO in time based
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO - dedup checksums or specified blocksize does not match.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: FIO - dedup checksums or specified blocksize does not match.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: FIO - dedup checksums or specified blocksize does not match.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: FIO - dedup checksums or specified blocksize does not match.
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO - dedup checksums or specified blocksize does not match.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Iuliu Rus <iuliur@xxxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Iuliu Rus <iuliur@xxxxxxxxxx>
• Re: fio queue depth and windows build.
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• fio queue depth and windows build.
  • From: Iuliu Rus <iuliur@xxxxxxxxxx>
• achieving a workload to get specific unique duplicate blocks
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: crash reports while running IO on raid0 btrfs
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• [Bug report] Runtime, IOPS, bandwidth recorded incorrectly if small size with time_based
  • From: Akash Verma <akashv@xxxxxxxxxx>
• Re: Unable to replay blktrace with mixed workload
  • From: Brandon Schwartz <schwartz.xn@xxxxxxxxx>
• Re: A probable minor mistake in HOWTO page
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• Re: A probable minor mistake in HOWTO page
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: A probable minor mistake in HOWTO page
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• Re: A probable minor mistake in HOWTO page
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: crash reports while running IO on raid0 btrfs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: crash reports while running IO on raid0 btrfs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Unable to replay blktrace with mixed workload
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Unable to replay blktrace with mixed workload
  • From: Brandon Schwartz <schwartz.xn@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• fio writing only around 50% of LUN capacity for fill_device=1
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Don't export state variable
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] Don't export state variable
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• fio trim bug
  • From: Neil Durbridge <neildurbridge@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: crash reports while running IO on raid0 btrfs
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• crash reports while running IO on raid0 btrfs
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: [PATCH] Fix mtd valgrind warning
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] Fix mtd valgrind warning
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: lex/yacc not configured properly.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• lex/yacc not configured properly.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Daniel Ehrenberg <dehrenberg@xxxxxxxxxx>
• Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Daniel Ehrenberg <dehrenberg@xxxxxxxxxx>
• [PATCH v2 7/7] mtd: example job file
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 6/7] mtd: ioengine
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 5/7] mtd: Import libmtd with modifications to make it compile
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 4/7] mtd: Add CONFIG_MTD to ./configure script
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 3/7] Collect a block-wise histogram of trim and write errors
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 2/7] Add new trimwrite rw= mode for trims preceding writes
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 1/7] Allow trim on any file type
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH v2 0/7] Framework for NAND lifetime testing
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 7/7] mtd: example job file
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 6/7] mtd: ioengine
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 5/7] mtd: Import libmtd with modifications to make it compile
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 4/7] mtd: Add CONFIG_MTD to ./configure script
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 3/7] Collect a block-wise histogram of trim and write errors
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 1/7] Allow trim on any file type
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• [PATCH 0/7] Framework for NAND lifetime testing
  • From: Dan Ehrenberg <dehrenberg@xxxxxxxxxxxx>
• Looping blktrace binary files
  • From: Brandon Schwartz <schwartz.xn@xxxxxxxxx>
• fio filename vs directory
  • From: Z Es <zahra.estaji68@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Samuel Shapiro <samuel.sh79@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Samuel Shapiro <samuel.sh79@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• FIO writes many empty files after ENOSPC from device.
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: FIO not generating multiple jobs for directories
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• RE: Need support about value IOPS Which FIO measured
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Samuel Shapiro <samuel.sh79@xxxxxxxxx>
• Re: during fio scenario with verify=meta some jobs fails
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: FIO not generating multiple jobs for directories
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO Building per ANdroid
  • From: Fabio Salvati <fabio.salvati@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO not generating multiple jobs for directories
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: Generating random data with FIO on directories returning null
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• Re: analyzing, visualizing, understanding and rating fio data
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Re: Generating random data with FIO on directories returning null
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Re: analyzing, visualizing, understanding and rating fio data
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• Generating random data with FIO on directories returning null
  • From: Srinivasa Chamarthy <chamarthy.raju@xxxxxxxxx>
• during fio scenario with verify=meta some jobs fails
  • From: Samuel Shapiro <samuel.sh79@xxxxxxxxx>
• Question regarding fio build system
  • From: Raphael Philipe <rapphil@xxxxxxxxx>
• Re: Latencies around 10 seconds for I/Os in a trace!!!
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• Re: analyzing, visualizing, understanding and rating fio data
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Re: Latencies around 10 seconds for I/Os in a trace!!!
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• A probable minor mistake in HOWTO page
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• Re: Latencies around 10 seconds for I/Os in a trace!!!
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• Re: Latencies around 10 seconds for I/Os in a trace!!!
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Latencies around 10 seconds for I/Os in a trace!!!
  • From: Mansour Shafaei Moghaddam <mansoor.shafaei@xxxxxxxxx>
• RE: Need support about value IOPS Which FIO measured
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• RE: fio always writes null bytes whatever I do
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: linux /dev and normal files
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: linux /dev and normal files
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• RE: Need support about value IOPS Which FIO measured
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Need support about value IOPS Which FIO measured
  • From: Nguyen Viet Dung <dungnguyenviet@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: FIO still returning 0 and writing file after bogus arguments
  • From: Jens Axboe <axboe@xxxxxxxxx>
• FIO for Android
  • From: "Fabio Salvati (fabiosalvati)" <fabiosalvati@xxxxxxxxxx>
• Re: Buggy behavior with zone, random IOs since specific commit
  • From: Akash Verma <akashv@xxxxxxxxxx>
• FIO still returning 0 and writing file after bogus arguments
  • From: Andy Moe <moea@xxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Buggy behavior with zone, random IOs since specific commit
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] In gettime.c, check for ARCH_CPU_CLOCK_WRAPS only ifdef ARCH_HAVE_CPU_CLOCK
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] In gettime.c, check for ARCH_CPU_CLOCK_WRAPS only ifdef ARCH_HAVE_CPU_CLOCK
  • From: Akash Verma <akashv@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Buggy behavior with zone, random IOs since specific commit
  • From: Akash Verma <akashv@xxxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio always writes null bytes whatever I do
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] init: fix exit status with bogus arguments
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio always writes null bytes whatever I do
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• [PATCH] init: fix exit status with bogus arguments
  • From: Zev Weiss <zev@xxxxxxxxxxxxxxxxx>
• Network to Disk Throughput Testing
  • From: Ben Randall <ben.randall.2011@xxxxxxxxx>
• fio always writes null bytes whatever I do
  • From: Urs Schaltegger <urs.schaltegger@xxxxxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Re: Rate for write IOPS read IOPS
  • From: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@xxxxxxxxxx>
• Re: Rate for write IOPS read IOPS
  • From: "Kulkarni, Vasu" <vasu.kulkarni@xxxxxxxxx>
• Rate for write IOPS read IOPS
  • From: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@xxxxxxxxxx>
• Re: Bug#779336: fio: calc_clat_percentiles() create unaligned access on armhf
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: increase max smalloc pools
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: increase max smalloc pools
  • From: Christian Ehrhardt <ehrhardt@xxxxxxxxxxxxxxxxxx>
• Re: Bug#779336: fio: calc_clat_percentiles() create unaligned access on armhf
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: Missing completions with libaio after context switch?
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Missing completions with libaio after context switch?
  • From: "Caldwell, Blake A." <blakec@xxxxxxxx>
• Re: [PATCH] fio: increase max smalloc pools
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: fix smalloc strdop allocation failure
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: increase max smalloc pools
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] fio: increase max smalloc pools
  • From: Christian Ehrhardt <ehrhardt@xxxxxxxxxx>
• [PATCH] fio: fix smalloc strdop allocation failure
  • From: Christian Ehrhardt <ehrhardt@xxxxxxxxxx>
• Re: diskutil output explained
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: fix cycles_start build issue
  • From: Christian Ehrhardt <ehrhardt@xxxxxxxxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• diskutil output explained
  • From: Georgios Koloventzos <g.koloventzos@xxxxxxxxx>
• Re: suggestion: patch to make per-thread IOPS more accurate
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] fio: fix cycles_start build issue
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] fio: fix cycles_start build issue
  • From: Christian Ehrhardt <ehrhardt@xxxxxxxxxxxxxxxxxx>
• Re: suggestion: patch to make per-thread IOPS more accurate
  • From: Andrew Theurer <atheurer@xxxxxxxxxx>
• Re: suggestion: patch to make per-thread IOPS more accurate
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Plain "./fio" segfaults on FreeBSD
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Plain "./fio" segfaults on FreeBSD
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: suggestion: patch to make per-thread IOPS more accurate
  • From: Mark Nelson <mark.a.nelson@xxxxxxxxx>
• Re: Stonewalled ?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Stonewalled ?
  • From: thoms <thoms@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: Stonewalled ?
  • From: Carl Zwanzig <cpz@xxxxxxxxxx>
• Stonewalled ?
  • From: thoms <thoms@xxxxxxxxxxxx>
• Plain "./fio" segfaults on FreeBSD
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Re: [PATCH] fix implicit function declaration on Android
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] Add missing pre-defined ARM arch compiler macro
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] Add missing pre-defined ARM arch compiler macro
  • From: Raphael Silva <rapphil@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: REPORT: High CPU utilization since 2.2.5
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• REPORT: High CPU utilization since 2.2.5
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Re: suggestion for fio --client to remove garbled output
  • From: Andrew Theurer <atheurer@xxxxxxxxxx>
• Re: suggestion: patch to make per-thread IOPS more accurate
  • From: Andrew Theurer <atheurer@xxxxxxxxxx>
• [PATCH] fix implicit function declaration on Android
  • From: enh <enh@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Potential leaks & errors on current trunk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Potential leaks & errors on current trunk
  • From: Erwan Velu <erwan@xxxxxxxxxxxx>
• Re: Potential leaks & errors on current trunk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Potential leaks & errors on current trunk
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: [RFC] [PATCH] Allow verification of random overwrites w/ba < bs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Potential leaks & errors on current trunk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [RFC] [PATCH] Allow verification of random overwrites w/ba < bs
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• Potential leaks & errors on current trunk
  • From: Erwan Velu <erwan@xxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Bug#776701: ssd-test 1g file size too small
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: Bug#776701: ssd-test 1g file size too small
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [RFC] [PATCH] Allow random overwrite workloads to write io_limit
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/1] gettime.h: use time_t instead of size_t for copy of tv_sec
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: [Suggestion] Header for --minimal output
  • From: Carl Zwanzig <cpz@xxxxxxxxxx>
• Re: [Suggestion] Header for --minimal output
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: [Suggestion] Header for --minimal output
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: [Suggestion] Header for --minimal output
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• [Suggestion] Header for --minimal output
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• suggestion: patch to make per-thread IOPS more accurate
  • From: Ben England <bengland@xxxxxxxxxx>
• suggested patch to let fio accept client ips from a file
  • From: Ben England <bengland@xxxxxxxxxx>
• suggestion for fio --client to remove garbled output
  • From: Ben England <bengland@xxxxxxxxxx>
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• [RFC] [PATCH] Allow random overwrite workloads to write io_limit
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• [PATCH 1/1] gettime.h: use time_t instead of size_t for copy of tv_sec
  • From: castor.fu@xxxxxxxxxxx
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SPC-1 profile
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] verify: Fix latency log for verify commands.
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• [PATCH] verify: Fix latency log for verify commands.
  • From: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
• fio: verify latency not reported correctly
  • From: Gwendal Grignou <gwendal@xxxxxxxxxxxx>
• Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Of <sendtold@xxxxxxxxx>
• Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• io_u->flags & IO_U_F_FLIGHT failed errors when using libaio
  • From: Lakshmi <sendtold@xxxxxxxxx>
• Re: verify_only broken? (was RE: )
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] configure: fix libnuma_v2 probe to work with -Werror
  • From: Jens Axboe <axboe@xxxxxxxxx>
• fio does not exit even if "bw" is below than "ratemin"
  • From: Kiran Patil <kiran@xxxxxxxxxxxxx>
• verify_only broken? (was RE: )
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• Re: Bug#776701: ssd-test 1g file size too small
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• Re: Help: FIO testing problem on arm64
  • From: "majun (F)" <majun258@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Help: FIO testing problem on arm64
  • From: "Kulkarni, Vasu" <vasu.kulkarni@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Help: FIO testing problem on arm64
  • From: Philip Keogh <pkeogh@xxxxxxxxxxxxxxx>
• [PATCH] configure: fix libnuma_v2 probe to work with -Werror
  • From: castor.fu@xxxxxxxxxxx
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Help: FIO testing problem on arm64
  • From: "majun (F)" <majun258@xxxxxxxxxx>
• [no subject]
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• Re: last_block() vs. min_bs when > blockalign
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] dedupe_percentage should work even if compress_percentage is not set
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: last_block() vs. min_bs when > blockalign
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• RE: last_block() vs. min_bs when > blockalign
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• last_block() vs. min_bs when > blockalign
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• [PATCH] dedupe_percentage should work even if compress_percentage is not set
  • From: Vasily Tarasov <tarasov@xxxxxxxxxxx>
• Re: sequential writing
  • From: Josh Carter <public@xxxxxxxxxxxxxx>
• sequential writing
  • From: "telecolega ." <telecolega@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: xfstests tests/ext4/304
  • From: Dmitry Monakhov <rjevskiy@xxxxxxxxx>
• xfstests tests/ext4/304
  • From: Xiaoguang Wang <wangxg.fnst@xxxxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Should io_limits/queue depth flushed persist while using verify_state?
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Should io_limits/queue depth flushed persist while using verify_state?
  • From: Sitsofe Wheeler <sitsofe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• analyzing, visualizing, understanding and rating fio data
  • From: Kiran Patil <kiran@xxxxxxxxxxxxx>
• Re: Questions about mmap ioengine
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] mmap backend broken
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] mmap backend broken
  • From: Yoshinori Sato <yo-satoh@xxxxxxxx>
• Re: Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] mmap backend broken
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: REPORT: FIO random read performance degradation without "norandommap" option
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Kulkarni, Vasu" <vasu.kulkarni@xxxxxxxxx>
• Re: REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• RE: REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• REPORT: FIO random read performance degradation without "norandommap" option
  • From: "Kudryavtsev, Andrey O" <andrey.o.kudryavtsev@xxxxxxxxx>
• Log Bug with fio-2.1.14 and Higher Causing fio Jobs to Time Out
  • From: George T Seese <george.t.seese@xxxxxxxxxxx>
• RE: Non-uniform randomness with drifting
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• RE: Non-uniform randomness with drifting
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Re: Non-uniform randomness with drifting
  • From: Mark Nelson <mark.a.nelson@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Non-uniform randomness with drifting
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Questions about mmap ioengine
  • From: Yigal Korman <yigal@xxxxxxxxxxxxx>
• [PATCH] mmap backend broken
  • From: Yoshinori Sato <yo-satoh@xxxxxxxx>
• Re: Capturing and Replaying with blktrace (but with compression and dedupable 0)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Capturing and Replaying with blktrace (but with compression and dedupable 0)
  • From: "Neto, Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@xxxxxxxxxx>
• Re: fio-2.1.14-17-g8671 in client/server mode: client continues to wait even after server is dead
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Jens Axboe <axboe@xxxxxx>
• fio-2.1.14-17-g8671 in client/server mode: client continues to wait even after server is dead
  • From: Surendar Chandra <surendar@xxxxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Jens Axboe <axboe@xxxxxx>
• fio-2.1.14-17-g8671 in client/server mode: client continues to wait even after server is dead
  • From: Surendar Chandra <surendar@xxxxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Jens Axboe <axboe@xxxxxx>
• Re: [PATCH] axmap: fix deadlock
  • From: Sedat Dilek <sedat.dilek@xxxxxxxxx>
• [PATCH] axmap: fix deadlock
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Scramble buffers not set by default unless set explicitly
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SSD write latency lower than read latency
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SSD write latency lower than read latency
  • From: Alireza Haghdoost <haghdoost@xxxxxxxxx>
• Scramble buffers not set by default unless set explicitly
  • From: Chris Wilson <Chris.Wilson@xxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SSD write latency lower than read latency
  • From: Georg Schönberger <gschoenberger@xxxxxxxxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: 'fio: no option found at offset'
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Fwd: Huge eta with R/W mix job and job hangs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Fwd: Huge eta with R/W mix job and job hangs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• 'fio: no option found at offset'
  • From: Bruce Cran <bruce@xxxxxxxxxxx>
• Questions about mmap ioengine
  • From: Yigal Korman <yigal@xxxxxxxxxxxxx>
• Re: Huge eta with Read/Write Mix Job and job hangs
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Huge eta with R/W mix job and job hangs
  • From: Lakshmi <sendtold@xxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: SSD write latency lower than read latency
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: SSD write latency lower than read latency
  • From: Erwan Velu <erwan@xxxxxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: SSD write latency lower than read latency
  • From: Matthew Eaton <m.eaton82@xxxxxxxxx>
• RE: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Stephen Nichols <Stephen.Nichols@xxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Random overwrite and verify workload
  • From: "Justin Eno (jeno)" <jeno@xxxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• RE: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Stephen Nichols <Stephen.Nichols@xxxxxxx>
• Re: SSD write latency lower than read latency
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• SSD write latency lower than read latency
  • From: Georg Schönberger <gschoenberger@xxxxxxxxxxxxxxxx>
• [Feature Request] AUTOMATICALLY DETERMINING LOAD TEST DURATION USING CONFIDENCE INTERVALS
  • From: Kiran Patil <kiran@xxxxxxxxxxxxx>
• Re: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: fio main thread got stuck over the weekend
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Sequential Commands are essentially random when in mixed sequential/random workloads
  • From: Stephen Nichols <Stephen.Nichols@xxxxxxx>
• RE: fio main thread got stuck over the weekend
  • From: "Elliott, Robert (Server Storage)" <Elliott@xxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Karthick Srinivasachary <karthick@xxxxxxxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Recent changes (master)
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Karthick Srinivasachary <karthick@xxxxxxxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Repeat given pattern with buffer_compress_percentage
  • From: Jens Axboe <axboe@xxxxxxxxx>