From: "Zhang, Helin" <helin.zhang@intel.com>
To: Alex Markuze <alex@weka.io>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] IOMMU and VF
Date: Fri, 9 Jan 2015 00:39:03 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7DC856@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKfHP0WgOnopVgRJQUXO2JKgEJkrYP5YKLrfOx8hhvGVvkO+Jw@mail.gmail.com>
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?
next prev parent reply other threads:[~2015-01-09 0:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 17:57 Alex Markuze
2015-01-09 0:39 ` Zhang, Helin [this message]
2015-01-09 12:45 ` Alex Markuze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F35DEAC7BCE34641BA9FAC6BCA4A12E70A7DC856@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=alex@weka.io \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).