[dpdk-dev] IOMMU and VF

[dpdk-dev] IOMMU and VF

[Alex Markuze]

Hi, Guys,
I'm trying to run a DPDK(1.7.1) application that has been previously tested
on Xen/VMware VM's. I have both iommu=pt and intel_iommu=on.
I would expect things to work as usual but unfortunately the VF I'm taking
is unable to send or receive any packets (The TXQ gets filled out, and the
packets never leave).

Looking at the demise I se this:
IOMMU: hardware identity mapping for device 0000:83:00.0
IOMMU: hardware identity mapping for device 0000:83:00.1

These are the bus addresses of the physical functions.
I don't know If I need to see the VF's listed here as well.

Any suggestions?

Re: [dpdk-dev] IOMMU and VF

[Zhang, Helin]

Hi Alex

Could you help to try 1.8? I remember there might a fix of supporting some newly mac types.
In addition, what's the kernel version of your host? We observed issues recently before kernel version 3.18. I'd suggest to try kernel 3.18.

Hopefully it is helpful!

Regards,
Helin

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
> Sent: Friday, January 9, 2015 1:57 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] IOMMU and VF
> 
> Hi, Guys,
> I'm trying to run a DPDK(1.7.1) application that has been previously tested on
> Xen/VMware VM's. I have both iommu=pt and intel_iommu=on.
> I would expect things to work as usual but unfortunately the VF I'm taking is
> unable to send or receive any packets (The TXQ gets filled out, and the packets
> never leave).
> 
> Looking at the demise I se this:
> IOMMU: hardware identity mapping for device 0000:83:00.0
> IOMMU: hardware identity mapping for device 0000:83:00.1
> 
> These are the bus addresses of the physical functions.
> I don't know If I need to see the VF's listed here as well.
> 
> Any suggestions?

Re: [dpdk-dev] IOMMU and VF

[Alex Markuze]

Thanks Zhang, I'm familiar with issue you have mentioned, but I don't
 think it is related.
The OS is a RHEL 6.5 which is kernel 2.6.32 (With what ever newer patches
RH have cherry picked).

Moving to DPDK 1.8 is not a viable option right now for us.
Could you please elaborate on the new mac types patches and how it can
relate to the issue at hand.

This feels like an iommu issue as we are able to configure the ports
successfully, but there is no traffic in or out.
Which leads me to believe that the RX/TX descriptors are at fault.
Another clue that I've already mentioned is these snippets from demise:
Looking at the demise I se this:
IOMMU: hardware identity mapping for device 0000:83:00.0
IOMMU: hardware identity mapping for device 0000:83:00.1

Which include the PF but not the VF. IOMMU has a separate translation table
for each peripheral device(just like the cpu has a separate translation
table and TLB for each process). I'm guessing that the IOMMU is not SRIOV
aware and should maintain a separate translation table for each virtual
function(unless I'm missing something). If this is true I would expect to
see that an identity ,capping has been set for the VFs as well.

It maybe some config issue.

Any advice would be appreciated.

Thanks




On Fri, Jan 9, 2015 at 2:39 AM, Zhang, Helin <helin.zhang@intel.com> wrote:

> Hi Alex
>
> Could you help to try 1.8? I remember there might a fix of supporting some
> newly mac types.
> In addition, what's the kernel version of your host? We observed issues
> recently before kernel version 3.18. I'd suggest to try kernel 3.18.
>
> Hopefully it is helpful!
>
> Regards,
> Helin
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
> > Sent: Friday, January 9, 2015 1:57 AM
> > To: dev@dpdk.org
> > Subject: [dpdk-dev] IOMMU and VF
> >
> > Hi, Guys,
> > I'm trying to run a DPDK(1.7.1) application that has been previously
> tested on
> > Xen/VMware VM's. I have both iommu=pt and intel_iommu=on.
> > I would expect things to work as usual but unfortunately the VF I'm
> taking is
> > unable to send or receive any packets (The TXQ gets filled out, and the
> packets
> > never leave).
> >
> > Looking at the demise I se this:
> > IOMMU: hardware identity mapping for device 0000:83:00.0
> > IOMMU: hardware identity mapping for device 0000:83:00.1
> >
> > These are the bus addresses of the physical functions.
> > I don't know If I need to see the VF's listed here as well.
> >
> > Any suggestions?
>