lkml.org 
[lkml]   [2014]   [Oct]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH] Perf Bench: Locking Microbenchmark

    * Tuan Bui <tuan.d.bui@hp.com> wrote:

    > > > +static const struct option options[] = {
    > > > + OPT_UINTEGER('s', "start", &start_nr_threads, "Numbers of processes to start"),
    > > > + OPT_UINTEGER('e', "end", &end_nr_threads, "Numbers of process to end"),
    > > > + OPT_UINTEGER('i', "increment", &increment_threads_by, "Number of threads to increment)"),
    > > > + OPT_UINTEGER('r', "runtime", &bench_dur, "Specify benchmark runtime in seconds"),
    > > > + OPT_END()
    > > > +};
    > >
    > > Is this the kind of parameters that AIM7 takes as well?
    > >
    > > In any case, this is a very nice benchmarking utility.
    >
    > Yes these parameters are similar to what AIM7 take except for
    > the runtime parameter. AIM7 does not have the option to
    > specify how long the benchmark will run. Also in AIM7 you can
    > also specify numbers of jobs per run which i did not include
    > since i added a runtime parameter for the benchmark.

    It might make sense to add that parameter - which would only be
    allowed if no runtime is specified, or so.

    I.e. to make it as easy for people to use this new tool when they
    come with AIM7 benchmarking knowledge.

    Thanks,

    Ingo


    \
     
     \ /
      Last update: 2014-10-09 10:02    [W:2.075 / U:0.260 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site