>
> Another suggestion, can you please compile PMD with debug enabled, it may
> give more details ?
>
>
>
> Best Regards,
>
> Olga
>
>
>
> *From:* Bill O'Hara [mailto:billtohara at gmail.com]
> *Sent:* Saturday, October 10, 2015 12:18 AM
> *To:* Olga Sher
, right?
>
> We did test this combination (dpdk2.1 and ofed3.1-3)on hypervisor on the
> PF and also on VM on VF, but in fact, I didn?t try to run DPDK on the VFs
> on hypervisor, I will check this.
>
> Meanwhile, can you please send the output of the application on the start
&
basic operation of
the upgraded OFED and firmware on those boxes.
Is there anything else we can check or confirm for you?
thanks
bill
On Thu, Oct 8, 2015 at 9:06 AM, Bill O'Hara wrote:
> Hi Olga
>
> Firmware is version 2.35.5100. Configuration details below.
>
> Thanks for a
.
>
>
> Original message
> From: Olga Shern
> Date:08/10/2015 7:55 AM (GMT+00:00)
> To: Bill O'Hara ,dev at dpdk.org
> Subject: RE: [dpdk-dev] Mellanox PMD failure w/DPDK-2.1.0 and
> MLNX_OFED-3.1-1.0.3
>
> Hi Bill,
>
> There shouldn?t be
Hello
I wonder if anyone can suggest why previously working dpdk code may fail in
the Mellanox pmd code in dpdk-2.1.0, seemingly due to failure to create a
"resource domain" via ibv_exp_create_res_domain(). I must admit I haven't
seen that verb before, and it appears to be returning null with no e
I see from the Mellanox PMD release notes:
http://www.mellanox.com/related-docs/prod_software/Mellanox_ConnectX3_ConnectX3Pro_DPDK_PMD_Release_Notes_v1.7-8_2.8.4.pdf
that the primary and secondary multi-process model is not supported. Though
it's not noted as a limitation in the DPDK guide here:
6 matches
Mail list logo
