DPDK patches and discussions
 help / color / mirror / Atom feed
From: Saber Rezvani <irsaber@zoho.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] IXGBE RX packet loss with 5+ cores
Date: Thu, 1 Nov 2018 10:12:32 +0330	[thread overview]
Message-ID: <b64615bb-ad97-e85f-58ac-d5adf3b375a3@zoho.com> (raw)
In-Reply-To: <561D2498.1060707@intel.com>

According to the problem to this thread -->

http://mails.dpdk.org/archives/dev/2015-October/024966.html


  Venkatesan, Venky mentioned the following reason:

To add a little more detail - this ends up being both a bandwidth and a
transaction bottleneck. Not only do you add an increased transaction
count, you also add a huge amount of bandwidth overhead (each 16 byte
descriptor is preceded by a PCI-E TLP which is about the same size). So
what ends up happening in the case where the incoming packets are
bifurcated to different queues (1 per queue) is that you have 2x the
number of transactions (1 for the packet and one for the descriptor) and
then we essentially double the bandwidth used because you now have the
TLP overhead per descriptor write.


But I couldn't figure out why we have bandwidth and transaction bottleneck.


Can anyone help me?


Best regards,

Saber

  reply	other threads:[~2018-11-01  6:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  2:57 Sanford, Robert
2015-10-13  5:18 ` Stephen Hemminger
2015-10-13 13:59   ` Bruce Richardson
2015-10-13 14:47     ` Sanford, Robert
2015-10-13 15:34       ` Venkatesan, Venky
2018-11-01  6:42         ` Saber Rezvani [this message]
2015-10-13 20:24       ` Alexander Duyck
2015-10-14  9:29         ` Bruce Richardson

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=b64615bb-ad97-e85f-58ac-d5adf3b375a3@zoho.com \
    --to=irsaber@zoho.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).