From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <97B23BED-1883-400F-A28C-752554717124@emc.com> In-Reply-To: <97B23BED-1883-400F-A28C-752554717124@emc.com> From: Mohanraj B Date: Mon, 29 Oct 2018 20:07:45 +0530 Message-ID: Subject: Re: Content-Type: multipart/alternative; boundary="000000000000d9eeb705795f037e" To: "Beierl, Mark" Cc: Jens Axboe , fio List-ID: --000000000000d9eeb705795f037e Content-Type: text/plain; charset="UTF-8" Thanks Axboe and Mark. On Mon 29 Oct, 2018, 7:50 PM Beierl, Mark, wrote: > On 2018-10-27, 12:55, "fio-owner@vger.kernel.org on behalf of Jens Axboe" > wrote: > > [EXTERNAL EMAIL] > Please report any suspicious attachments, links, or requests for > sensitive information. > > > On 10/26/18 6:54 AM, Mohanraj B wrote: > > Hello, > > > > I am trying to check how option --clocksource works. > > > > > > bash# fio --name job1 --size 10m --clocksource 2 > > valid values: gettimeofday Use gettimeofday(2) for timing > > : clock_gettime Use clock_gettime(2) for timing > > : cpu Use CPU private clock > > > > fio: failed parsing clocksource=2 > > > > bash# fio --name job1 --size 10m --clocksource gettimeofday(2) > > bash: syntax error near unexpected token `(' > > > > Below command works fine. > > bash# fio --name job1 --size 10m --clocksource gettimeofday > > > > It runs without error but quiet not sure how to see the effect of > this > > option. also tried other options - clock_gettime, cpu gettimeofday > and > > dont see any difference. > > > > Also is there any error in documentation passing gettimeofday(2) > > throws parse error. > > The format is 'value' 'help', so you'd want to do: > > --clocksource=gettimeofday > > for instance. > > -- > Jens Axboe > > Hello, Mohanraj > > The help output that you see above states that using > --clocksource=gettimeofday will use the gettimeofday function as defined in > the man page in the section (2), which is where all the system calls > manuals are stored. The (2) is not meant to be part of the command line, > it is part of the description of the help text, which tells you where to > find more information on what is being used to implement the clocksource. > > Hope that helps clarify the help text. > > Regards, > Mark > > > > --000000000000d9eeb705795f037e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Axboe and Mark.

On Mon 29 Oct, 2018, 7:50 PM Beierl, Mark, <Mark.Beierl@dell.com> wrote:
On 2018-10-27, 12:55, "fio-ow= ner@vger.kernel.org on behalf of Jens Axboe" <fio-owner@= vger.kernel.org on behalf of axboe@kernel.dk> wrote:

=C2=A0 =C2=A0 [EXTERNAL EMAIL]
=C2=A0 =C2=A0 Please report any suspicious attachments, links, or requests = for sensitive information.


=C2=A0 =C2=A0 On 10/26/18 6:54 AM, Mohanraj B wrote:
=C2=A0 =C2=A0 > Hello,
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > I am trying to check how option --clocksource works.
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > bash# fio --name job1 --size 10m --clocksource 2
=C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0valid values: gettimeof= day Use gettimeofday(2) for timing
=C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0: clock_gettime Use clock_gettime(2) for timing
=C2=A0 =C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0: cpu=C2=A0 =C2=A0 =C2=A0 =C2=A0 Use CPU private clock<= br> =C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > fio: failed parsing clocksource=3D2
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > bash# fio --name job1 --size 10m --clocksource gettimeof= day(2)
=C2=A0 =C2=A0 > bash: syntax error near unexpected token `('
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > Below command works fine.
=C2=A0 =C2=A0 > bash# fio --name job1 --size 10m --clocksource gettimeof= day
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > It runs without error but quiet not sure how to see the = effect of this
=C2=A0 =C2=A0 > option. also tried other options - clock_gettime, cpu ge= ttimeofday and
=C2=A0 =C2=A0 > dont see any difference.
=C2=A0 =C2=A0 >
=C2=A0 =C2=A0 > Also is there any error in documentation passing gettime= ofday(2)
=C2=A0 =C2=A0 > throws parse error.

=C2=A0 =C2=A0 The format is 'value' 'help', so you'd wa= nt to do:

=C2=A0 =C2=A0 --clocksource=3Dgettimeofday

=C2=A0 =C2=A0 for instance.

=C2=A0 =C2=A0 --
=C2=A0 =C2=A0 Jens Axboe

Hello, Mohanraj

The help output that you see above states that using --clocksource=3Dgettim= eofday will use the gettimeofday function as defined in the man page in the= section (2), which is where all the system calls manuals are stored.=C2=A0= The (2) is=C2=A0 not meant to be part of the command line, it is part of t= he description of the help text, which tells you where to find more informa= tion on what is being used to implement the clocksource.

Hope that helps clarify the help text.

Regards,
Mark



--000000000000d9eeb705795f037e--