From: Alexander Belyakov <abelyako@gmail.com>
To: Prashant Upadhyaya <prashant.upadhyaya@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Surprisingly high TCP ACK packets drop counter
Date: Tue, 5 Nov 2013 13:29:57 +0400 [thread overview]
Message-ID: <CAAQJX_SAUYaNbXrsLaTTaBfR_Mtr5A4ZDwskDNMXEd3SsKx6fA@mail.gmail.com> (raw)
In-Reply-To: <C7CE7EEF248E2B48BBA63D0ABEEE700C45DF9E3F02@GUREXMB01.ASIAN.AD.ARICENT.COM>
Hello,
On Mon, Nov 4, 2013 at 7:06 AM, Prashant Upadhyaya <
prashant.upadhyaya@aricent.com> wrote:
> Hi Alexander,
>
> Please confirm if the patch works for you.
>
Disabling RSC (DPDK 1.3) indeed brings ACK flood forwarding performance to
14,5+ Mpps. No negative side affects were discovered so far, but we're
still testing.
>
> @Wang, are you saying that without the patch the NIC does not fan out the
> messages properly on all the receive queues ?
> So what exactly happens ?
>
>
Patch deals with RSC (receive side coalescing) but not RSS (receive side
scaling).
> Regards
> -Prashant
>
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alexander Belyakov
> Sent: Monday, November 04, 2013 1:51 AM
> To: Wang, Shawn
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Surprisingly high TCP ACK packets drop counter
>
> Hi,
>
> thanks for the patch and explanation. We have tried DPDK 1.3 and 1.5 -
> both have the same issue.
>
> Regards,
> Alexander
>
>
next prev parent reply other threads:[~2013-11-05 9:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 13:43 Alexander Belyakov
2013-11-01 14:54 ` Wang, Shawn
2013-11-01 15:14 ` Thomas Monjalon
2013-11-02 5:32 ` Prashant Upadhyaya
2013-11-03 20:20 ` Alexander Belyakov
2013-11-04 3:06 ` Prashant Upadhyaya
2013-11-05 9:29 ` Alexander Belyakov [this message]
2013-11-05 10:10 ` Olivier MATZ
2013-11-05 11:59 ` Alexander Belyakov
2013-11-05 14:40 ` Prashant Upadhyaya
2013-11-05 17:03 ` Wang, Shawn
2013-11-06 8:42 ` Alexander Belyakov
2013-11-02 5:29 ` Prashant Upadhyaya
2013-11-03 20:32 ` Alexander Belyakov
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=CAAQJX_SAUYaNbXrsLaTTaBfR_Mtr5A4ZDwskDNMXEd3SsKx6fA@mail.gmail.com \
--to=abelyako@gmail.com \
--cc=dev@dpdk.org \
--cc=prashant.upadhyaya@aricent.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).