Hi, Would changing the HOWTO to say: "Make the job containing the stonewall parameter wait for preceding jobs in the job file to exit before starting." be any clearer? What did you find that made you expect the original behaviour and what did you find that made you change your understanding? On 12 July 2017 at 08:01, Ido Ben-Tsion <idob@xxxxxxxxxxxxx> wrote: > ok, I understand. I didn't think of stonewall as being part of a job. > I thought of it as a separator between jobs, unrelated to any specific > job. which is not what the documentation explains. > > On Wed, Jul 12, 2017 at 9:26 AM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >> Hi, >> >> On 12 July 2017 at 06:13, Ido Ben-Tsion <idob@xxxxxxxxxxxxx> wrote: >>> fio version: fio-2.21-37-ga2c9 >>> >>> fio file excerpt: >>> [global] >>> ioengine=sg >>> invalidate=1 >>> ramp_time=5 >>> iodepth=16 >>> runtime=300 >>> time_based >>> bs=64k >>> norandommap >>> loops=5 >>> >>> [seq_read-2-jobs] >>> rw=read >>> numjobs=2 >>> stonewall >>> >>> [randread] >>> rw=randread >>> [seq_write] >>> rw=write >>> stonewall >>> ... >>> >>> In the report, I see jobs with groupid 0 which are not supposed to be >>> on same group: >>> ...,jobname,groupid,... >>> ...,seq_read-2-jobs,0,... >>> ...,seq_read-2-jobs,0,... >>> ...,randread,0,... >>> ...,seq_write,1,... >> >> I'm not sure I follow - which jobs are wrong? Looking at the opening >> sentence explanation (and the alternative name) for stonewall in the >> HOWTO (http://fio.readthedocs.io/en/latest/fio_man.html#cmdoption-arg-stonewall >> ) seems to describe the behaviour you're seeing. >> >> Can you be more explicit as to the problem? -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
