> > Previously, max_socket was set to the highest numbered socket with
> > an enabled lcore. The intent is to set it to the highest socket
> > regardless of it being enabled.
> >
> > Change-Id: I6306af0f90aa3c1fc5ffed75d1eed8297d29e132
> > Signed-off-by: Stephen Hurd
>
> Acked-by: Pablo de Lara
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Stephen Hurd
> Sent: Wednesday, January 13, 2016 10:24 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH v2] app/testpmd Fix max_socket detection
>
> Previously, max_socket was set to
t; -Original Message-
> From: Bruce Richardson [mailto:bruce.richardson at intel.com]
> Sent: Thursday, January 14, 2016 5:44 AM
> To: Stephen Hurd
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd Fix max_socket detection
>
> On Wed, Jan 13,
Found it...
http://www.dpdk.org/ml/archives/dev/2015-December/030564.html
-- Stephen Hurd
-Original Message-
From: Bruce Richardson [mailto:bruce.richard...@intel.com]
Sent: Thursday, January 14, 2016 5:44 AM
To: Stephen Hurd
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] app
L: Error - exiting with code: 1
>> Cause: The socket number should be < 1
>>
His example command was:
./testpmd -c 0x3 -n 4 -- -i -socket-num=1
-- Stephen Hurd
-Original Message-
From: Bruce Richardson [mailto:bruce.richard...@intel.com]
Sent: Thursday, January 14, 2016 5
On Wed, Jan 13, 2016 at 02:23:36PM -0800, Stephen Hurd wrote:
> Previously, max_socket was set to the highest numbered socket with
> an enabled lcore. The intent is to set it to the highest socket
> regardless of it being enabled.
>
Can you clarify why this changes is necessary? Is it causing a
Previously, max_socket was set to the highest numbered socket with
an enabled lcore. The intent is to set it to the highest socket
regardless of it being enabled.
Change-Id: I6306af0f90aa3c1fc5ffed75d1eed8297d29e132
Signed-off-by: Stephen Hurd
v2: Forgot to commit before sending email... sorry
7 matches
Mail list logo