DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yan Fridland <yan@asocsnetworks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] : rx_no_dma_resources starts climbing on Intel 82599 SR-IOV ports
Date: Tue, 11 Jul 2017 16:41:39 +0000	[thread overview]
Message-ID: <AM3PR06MB0846E4C0DABAB1A1DC80968A3AE0@AM3PR06MB084.eurprd06.prod.outlook.com> (raw)

Hello All,

Perhaps you can shade some light on an interesting problem we have.

I am working with Intel 82599 NICs in a SR-IOV mode. After several hours of running traffic we checked port statistics on a host and saw that the counter rx_no_dma_resources began climbing on some ports.
At that exact time the VM applications connected to that ports showed packet loss and crashed.

First question, do you have a clue what is it related to? (I run the same application on all ports but not all of them experience such thing)

After digging a bit I saw that the RX descriptors ring size on the host ports was defined to 256 out of 4096 possible (I used ehttool -G). I know that in DPDK I define each port's RX queue to be 256 descriptors, but this is done per VM port which means per VF of the physical NIC.


  *   Do you know what is the relationship, if any, between the number of descriptors defined in DPDK per VM port (VF on host) using rte_eth_rx_queue_setup () and the number of descriptors defined on Host per physical port (using ethtool -g <dev> rx <desc num>) ?
Seems to me that they don't effect one another but perhaps I am wrong.


Thanks,
Yan

                 reply	other threads:[~2017-07-11 16:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AM3PR06MB0846E4C0DABAB1A1DC80968A3AE0@AM3PR06MB084.eurprd06.prod.outlook.com \
    --to=yan@asocsnetworks.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).