DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jose Gavine Cueto <pepedocs@gmail.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] intel x540-at2
Date: Fri, 3 Jan 2014 17:09:03 +0800	[thread overview]
Message-ID: <CAJ5bv6F_qEj8pUhGLt6qvR02k+zZLfVjD_Geg4YJSOK2moxCaQ@mail.gmail.com> (raw)
In-Reply-To: <201401021524.14069.thomas.monjalon@6wind.com>

Sorry I accidentally excluded the list.  I've pasted the replies:


---------------------------------------------------------------------------------------------------------------------------
I see thanks.

I'm actually running my DPDK application on a guest OS but I'm always
getting an invalid instruction error.  I was thinking that this was due to
ixgbevf driver in guest that commands the host driver which is not-fully
supported by DPDK, and consequently ran an invalid instruction.  This
brings me back to the questions:

Are SR-IOV virtual function drivers supported by DPDK  PMD (I guess yes) ?
 If yes, does the physical function (host) driver affects the DPDK
application in any way especially if it isn't fully supported yet by DPDK?

I've tried looking at incompatibility issues with respect to compiler and
processor archs. but it seems OK to me.

Thanks,
Pepe

----------------------------------------------------------------------------------------------------------------------------

SR-IOV is supported. There are dependencies with PF driver which handle NIC
configuration. VF/PF communication is done via mailbox.

Please use the list.


Thomas



On Thu, Jan 2, 2014 at 10:24 PM, Thomas Monjalon
<thomas.monjalon@6wind.com>wrote:

> 23/12/2013 10:18, Jose Gavine Cueto :
> > I can't find a MACRO for this nic in rte_pci_dev_ids.h, does this mean
> this
> > isn't supported as of this moment ?
>
> Yes
> But probably that
>         hw->mac.type = ixgbe_mac_X540
> apply also to x540-at2.
>
> Please to try to add it and send the patch if it works.
> --
> Thomas
>



-- 
To stop learning is like to stop loving.

  reply	other threads:[~2014-01-03  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  9:18 Jose Gavine Cueto
2014-01-02 14:24 ` Thomas Monjalon
2014-01-03  9:09   ` Jose Gavine Cueto [this message]
2014-01-03  9:16     ` Jose Gavine Cueto
2014-01-03  9:56       ` Thomas Monjalon
2014-01-03 10:09         ` Jose Gavine Cueto
2014-01-03 10:26           ` Thomas Monjalon
2014-01-03 10:31             ` Jose Gavine Cueto
2014-01-03 13:43               ` Venkatesan, Venky
2014-01-03 13:59                 ` Thomas Monjalon
2014-01-05 14:31                 ` Jose Gavine Cueto
2014-01-05 14:54                   ` Thomas Monjalon
2014-01-06  6:03                     ` Jose Gavine Cueto
2014-01-08  6:13                       ` Jose Gavine Cueto

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=CAJ5bv6F_qEj8pUhGLt6qvR02k+zZLfVjD_Geg4YJSOK2moxCaQ@mail.gmail.com \
    --to=pepedocs@gmail.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    /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).