Don't start new groups for numjobs=

No point in doing that, and it makes two identical jobs behave
differently if typed manually or implicitly with numjobs=x

Signed-off-by: Jens Axboe <jens.axboe@oracle.com>

diff --git a/init.c b/init.c
index 047da8d553bb6a7b366127062554d1a9a421f0dd..f72112795ce09184c385d3ea5f1517c1bc9ab183 100644 (file)
--- a/init.c
+++ b/init.c
@@ -529,8 +529,7 @@ static int add_job(struct thread_data *td, const char *jobname, int job_add_num)
        td->ts.bw_stat[0].min_val = td->ts.bw_stat[1].min_val = ULONG_MAX;
        td->ddir_nr = td->o.ddir_nr;
 
-       if ((td->o.stonewall || td->o.numjobs > 1 || td->o.new_group)
-            && prev_group_jobs) {
+       if ((td->o.stonewall || td->o.new_group) && prev_group_jobs) {
                prev_group_jobs = 0;
                groupid++;
        }