From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Dpdk ixgbe driver bug?
Date: Wed, 27 Sep 2017 11:58:50 +0800 [thread overview]
Message-ID: <CAOE=1Z0THrS5uHe5uby25NeHbku18r6jNLsB2peDKwGHqSOBoA@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z3ZJSZPbONRojqdCe8PwK+nO_buMjW0GPBcOarCNO8G_A@mail.gmail.com>
switch means hardware switch attach this PC, not ovs-dpdk
2017-09-27 11:57 GMT+08:00 Sam <batmanustc@gmail.com>:
> Hi all,
>
> I'm running ovs-dpdk using ixgbe driver with sriov mode. My topology is:
> vf(ens16) and pf(eth0) is from netdevice 1; vf(ens161) and pf(eth1) is from
> netdevice 2. Then linux kernel driver bond ens16 and ens161 into bond1,
> ovs-dpdk bond eth0 and eth1 into dpdkb2 as ovs-dpdk port.
>
> I found that, the ovs-dpdk running for about half month, the bond1 and
> dpdkb2 port will block and no packets could pass through, then I have to
> restart ovs-dpdk, then it's OK.
>
> I think there is bug in ixgbe vf/pf driver, as I use standard ovs-dpdk,
> and when bug happen, I could not capture packet on dond1 by tcpdump. And
> the switch is OK, so the packet could only block or drop in ixgbe vf/pf
> driver.
>
> How to fix this bug? Thank you~
>
prev parent reply other threads:[~2017-09-27 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 3:57 Sam
2017-09-27 3:58 ` Sam [this message]
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='CAOE=1Z0THrS5uHe5uby25NeHbku18r6jNLsB2peDKwGHqSOBoA@mail.gmail.com' \
--to=batmanustc@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).