From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Tim.Bird@sony.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Sony.onmicrosoft.com; 
	s=selector1-Sony-onmicrosoft-com;
	h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
	bh=ISWyFH5trHQSZosDW7O8cqskYP7PG7+Mmm++Prbmqp4=;
	b=eJRteFi4kN49uJHM8laq1xAw/KBvhyrr3rMexviBkWNB6lZumiGvoaXXq5yme7UZXCv9CHPjE3MbtmSRtb2bLVyhFqau4iIFtd0eXDTNLL8JL1TC3rYpvF2Q2ooIa8+0ZoH88kWSKg/rxq1YlGke6w/qWuet5OPQN+Sp49KCrbU=
From: <Tim.Bird@sony.com>
Date: Fri, 16 Nov 2018 03:31:02 +0000
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF88A413EA@USCULXMSG01.am.sony.com>
References: <1542255972-10772-1-git-send-email-qiutt@cn.fujitsu.com>
	<1542255972-10772-7-git-send-email-qiutt@cn.fujitsu.com>
	<ECADFF3FD767C149AD96A924E7EA6EAF88A410C9@USCULXMSG01.am.sony.com>
	<18659EB99691CD459052A63DBE05D1F9017EA25CCC@G08CNEXMBPEKD02.g08.fujitsu.local>
In-Reply-To: <18659EB99691CD459052A63DBE05D1F9017EA25CCC@G08CNEXMBPEKD02.g08.fujitsu.local>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Fuego] [PATCH 07/15] ptsematest: fix unavailable cpu num of
 PARAMS
List-Id: Mailing list for the Fuego test framework
	<fuego.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/fuego/>
List-Post: <mailto:fuego@lists.linuxfoundation.org>
List-Help: <mailto:fuego-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/fuego>,
	<mailto:fuego-request@lists.linuxfoundation.org?subject=subscribe>
To: qiutt@cn.fujitsu.com
Cc: fuego@lists.linuxfoundation.org

> -----Original Message-----
> From: Qiu, Tingting=20
>=20
> Hi,Tim
>=20
> > -----Original Message-----
> > From: Tim.Bird@sony.com [mailto:Tim.Bird@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.
>=20
> 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
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> -t       --threads         one thread per available processor
> -t [NUM] --threads=3DNUM     number of threads:
>                            without NUM, threads =3D max_cpus
>                            without -t default =3D 1
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
>=20
> 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