[Fuego] [PATCH 07/15] ptsematest: fix unavailable cpu num of PARAMS

Tim.Bird at sony.com Tim.Bird at sony.com
Fri Nov 16 03:31:02 UTC 2018


> -----Original Message-----
> From: Qiu, Tingting 
> 
> Hi,Tim
> 
> > -----Original Message-----
> > From: Tim.Bird at sony.com [mailto:Tim.Bird at sony.com]
> > > -----Original Message-----
> > > From: Qiu Tingting on Wednesday, November 14, 2018 8:26 PM
> > >
> > > Cmd ptsematest has -t num parameter.
> > > When cpu num is not setted, default value is max num of cpu.
> > > Maybe some of cpu is not working, so we should set the available cpu
> num.
> >
> > Can you explain this more?  This change adjusts
> > the code to have ptsematest use the number of cpus reported
> > by /proc/cpuinfo.   This seems like it would be the maximum number of
> > cpus on the system.
> 
> Referring to help information, we know that '-t' parameter means one
> thread per available processor.
> So, it would be the maximum available number of cpus on the system.
> ptsematest usage
> ===========================
> -t       --threads         one thread per available processor
> -t [NUM] --threads=NUM     number of threads:
>                            without NUM, threads = max_cpus
>                            without -t default = 1
> ===========================
> 
> By default, threads num is setted by sysconf(_SC_NPROCESSORS_CONF).
> But, value of _SC_NPROCESSORS_CONF is maximum number of cpus on
> system,
> which include available processor and unavailable processor.

So, does /proc/cpuinfo not report the unavailable processors?

 -- Tim



More information about the Fuego mailing list