Flexible I/O Tester development
 help / color / mirror / Atom feed
* [PATCH] HOWTO: Fix description of grouping behavior with numjobs
@ 2012-10-04 22:58 Akash Verma
  2012-10-05 11:34 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: Akash Verma @ 2012-10-04 22:58 UTC (permalink / raw)
  To: fio; +Cc: Akash Verma


Signed-off-by: Akash Verma <akashv@google.com>
---
 HOWTO |   25 ++++++++++++-------------
 1 files changed, 12 insertions(+), 13 deletions(-)

diff --git a/HOWTO b/HOWTO
index 1362aea..cdff07a 100644
--- a/HOWTO
+++ b/HOWTO
@@ -1053,22 +1053,21 @@ wait_for_previous Wait for preceeding jobs in the job file to exit, before
 		points in the job file. A stone wall also implies starting
 		a new reporting group.
 
-new_group	Start a new reporting group. If this option isn't given,
-		jobs in a file will be part of the same reporting group
-		unless separated by a stone wall (or if it's a group
-		by itself, with the numjobs option).
+new_group	Start a new reporting group. See: group_reporting.
 
 numjobs=int	Create the specified number of clones of this job. May be
 		used to setup a larger number of threads/processes doing
-		the same thing. We regard that grouping of jobs as a
-		specific group.
-
-group_reporting	If 'numjobs' is set, it may be interesting to display
-		statistics for the group as a whole instead of for each
-		individual job. This is especially true of 'numjobs' is
-		large, looking at individual thread/process output quickly
-		becomes unwieldy. If 'group_reporting' is specified, fio
-		will show the final report per-group instead of per-job.
+		the same thing. Each thread is reported separately; to see
+		statistics for all clones as a whole, use group_reporting in
+		conjunction with new_group.
+
+group_reporting	It may sometimes be interesting to display statistics for
+		groups of jobs as a whole instead of for each individual job. This is
+		especially true if 'numjobs' is used; looking at individual
+		thread/process output quickly becomes unwieldy. To see the final report
+		per-group instead of per-job, use 'group_reporting'. Jobs in a file
+		will be part of the same reporting group, unless if separated by a
+		stonewall, or by using 'new_group'.
 
 thread		fio defaults to forking jobs, however if this option is
 		given, fio will use pthread_create(3) to create threads
-- 
1.7.7.3


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] HOWTO: Fix description of grouping behavior with numjobs
  2012-10-04 22:58 [PATCH] HOWTO: Fix description of grouping behavior with numjobs Akash Verma
@ 2012-10-05 11:34 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2012-10-05 11:34 UTC (permalink / raw)
  To: Akash Verma; +Cc: fio

On 2012-10-05 00:58, Akash Verma wrote:
> Signed-off-by: Akash Verma <akashv@google.com>

Thanks, this looks good, applied.

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-10-05 11:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-04 22:58 [PATCH] HOWTO: Fix description of grouping behavior with numjobs Akash Verma
2012-10-05 11:34 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox