DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Martin Weiser <martin.weiser@allegro-packets.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i40e: disabling flow control makes XL710 NIC discard all packets
Date: Wed, 4 Nov 2015 14:32:34 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A9354F7@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <5639DB34.2070500@allegro-packets.com>

Hi Martin

Thank you very much for reporting the issue!
Could you help to add more detailed steps and other information?
We will try to reproduce what have seen in our lab, and then debug.

Regards,
Helin

> -----Original Message-----
> From: Martin Weiser [mailto:martin.weiser@allegro-packets.com]
> Sent: Wednesday, November 4, 2015 6:17 PM
> To: Zhang, Helin; dev@dpdk.org
> Subject: i40e: disabling flow control makes XL710 NIC discard all packets
> 
> Hi Helin,
> 
> I have been doing some tests with the current DPDK master to see if the issues
> we had with performance and statistics have improved.
> In our own applications we usually disable flow control using the following code:
> 
> struct rte_eth_fc_conf fc_conf = { .mode = RTE_FC_NONE }; int ret =
> rte_eth_dev_flow_ctrl_set(port_id, &fc_conf);
> 
> In DPDK 2.1 this did not cause any problems with XL710 NICs but with the current
> master the NIC will not receive any packets and they are all counted in ierrors and
> imissed.
> The return value of rte_eth_dev_flow_ctrl_set does not indicate an error so it
> seems like something is going wrong here.

> 
> Regards,
> Martin


  reply	other threads:[~2015-11-04 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 10:17 Martin Weiser
2015-11-04 14:32 ` Zhang, Helin [this message]
2015-11-05 10:14   ` Martin Weiser

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A9354F7@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=martin.weiser@allegro-packets.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).