Hi
I reported the same issue 2 weeks ago
http://dpdk.org/ml/archives/dev/2017-February/056930.html
You can reproduce it forcing testpmd to allocate memory only from node 1,
for example:
/tmp/testpmd -d /home/micro/lib/librte_pmd_i40e.so -c 0xFFFC000 -w
:81:00.0 -w :81:00.1 -n 4 --socket-
Hi
I am not able to reproduce the issue anymore with nvm 5.05 + 17.02-rc2
(with LSC disabled)
Lesson learned: always upgrade to latest versions first.
Thanks to everyone for the support
Regards
Ivan
On 7 February 2017 at 15:56, Olivier MATZ wrote:
> Hi Helin,
>
> On Mon, 6 Feb 2017 01:36:45 +
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ivan Nardi
>> Sent: Monday, February 6, 2017 9:13 PM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] 17.02-rc2: i40e and LSC
>>
>> Hi guys
>> we are upgrading our application from dpdk 16.11 to 17.02-rc2 and
from SOCKET_ID_ANY of from the exact node associated with the network
device
Thanks for looking into that
Ivan
On 7 February 2017 at 02:49, Zhang, Helin wrote:
>
>
>> -Original Message-----
>> From: Ivan Nardi [mailto:nardi.i...@gmail.com]
>> Sent: Tuesday, Februa
t;
> Thank you!
>
> Regards
> Qi
>
>> -Original Message-
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ivan Nardi
>> Sent: Monday, February 6, 2017 4:19 AM
>> To: dev@dpdk.org
>> Cc: Olivier MATZ ; Christos Ricudis
>> ; Rowden,
Hi
With dpdk 17.02-rc2 i40e driver doesn't load at all when memory
allocation is restricted on numa node 1 (on system with more than 1
node, obviously)
[root@micro ~]# /tmp/testpmd -d /home/micro/lib/librte_pmd_i40e.so -c
0xFFFC000 -w :81:00.0 -w :81:00.1 -n 4 --socket-mem=0,8192 --
-i -
Hi guys
we are upgrading our application from dpdk 16.11 to 17.02-rc2 and we are
facing a strange behavior with i40e driver and LSC
If we call rte_eth_dev_configure() with port_conf.intr_conf.lsc = 1, the
call always failed with error
Configuring Port 0 (socket 1)
rte_eth_dev_configure: driver net
HI
same issue with 17.02-rc2
It seems to me the problem I am facing is similar to the ones reported in
these mails; if not, I apologize to have used this thread
Ivan
On 5 February 2017 at 16:30, Ivan Nardi wrote:
> Hi guys
> any updates on this issue?
> We are facing a very simila
Hi guys
any updates on this issue?
We are facing a very similar problem.
We have a server with 4 nics X710 4*10Gbit and the dpdk randomly failed to
start with the error:
PMD: eth_i40e_dev_init(): FW 4.40 API 1.4 NVM 04.05.03 eetrack 80001cd8
PMD: eth_i40e_dev_init(): Failed to sync phy type: -95
9 matches
Mail list logo
