DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chas Williams <3chas3@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] bnx2x driver and 57800 versus 57810
Date: Tue, 26 Jan 2016 19:13:18 -0500	[thread overview]
Message-ID: <1453853598.28524.23.camel@gmail.com> (raw)

I have to practically identical systems, same hypervisor on each (Centos
7.x).  In one, I have a 57800 card which works fine with DPDK with
SRIOV.  In the other, I have a 57810 card which doesn't work with SRIOV.

For the 57810 I have tracked this down to the status block in the VF
failing to be updated.  The linux driver works fine but it appears to
use a slightly different scheme -- writing some sort of fastpath status
block generation per interrupt.

Does anyone have any suggestions or a programming guide for this device?

             reply	other threads:[~2016-01-27  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27  0:13 Chas Williams [this message]
2016-01-27  7:32 ` Harish Patil
2016-01-27 15:58   ` Chas Williams
2016-06-13 14:11     ` Chas Williams

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=1453853598.28524.23.camel@gmail.com \
    --to=3chas3@gmail.com \
    --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).