dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Wang, Shawn" <xingbow-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Surprisingly high TCP ACK packets drop counter
Date: Fri, 01 Nov 2013 16:14:40 +0100	[thread overview]
Message-ID: <3485100.RiP6AQCKWQ@x220> (raw)
In-Reply-To: <CE990D16.3B335%xingbow-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.org>

Hello,

01/11/2013 14:54, Wang, Shawn :
> We had the same problem before. It turned out that RSC (receive side
> coalescing) is enabled by default in DPDK. So we write this naïve patch to
> disable it. This patch is based on DPDK 1.3. Not sure 1.5 has changed it
> or not.
> After this patch, ACK rate should go back to 14.5Mpps. For details, you
> can refer to Intel® 82599 10 GbE Controller Datasheet. (7.11 Receive Side
> Coalescing).

Please, could you resend this patch with a properly formatted commit log,
in order to review it for integration ?

Thank you
-- 
Thomas

  parent reply	other threads:[~2013-11-01 15:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 13:43 Surprisingly high TCP ACK packets drop counter Alexander Belyakov
     [not found] ` <CAAQJX_SWNBvBDTz3o_7Wo17-redr3Sygwq4pxBMTk3oYTwFhRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-01 14:54   ` Wang, Shawn
     [not found]     ` <CE990D16.3B335%xingbow-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.org>
2013-11-01 15:14       ` Thomas Monjalon [this message]
2013-11-02  5:32       ` Prashant Upadhyaya
2013-11-03 20:20       ` Alexander Belyakov
     [not found]         ` <CAAQJX_SL0UHzLDzsN-vRn449Cwyu0fphfyYZyovjfcKmWLJDKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-04  3:06           ` Prashant Upadhyaya
     [not found]             ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DF9E3F02-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-05  9:29               ` Alexander Belyakov
     [not found]                 ` <CAAQJX_SAUYaNbXrsLaTTaBfR_Mtr5A4ZDwskDNMXEd3SsKx6fA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 10:10                   ` Olivier MATZ
     [not found]                     ` <5278C412.4000204-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-11-05 11:59                       ` Alexander Belyakov
     [not found]                         ` <CAAQJX_Q9cOsKspauRMC9aJwAR+o3FhztxsiT4cdBtandJLsE9Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-05 14:40                           ` Prashant Upadhyaya
     [not found]                             ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DF9E40F4-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
2013-11-05 17:03                               ` Wang, Shawn
2013-11-06  8:42                               ` Alexander Belyakov
2013-11-02  5:29   ` Prashant Upadhyaya
     [not found]     ` <C7CE7EEF248E2B48BBA63D0ABEEE700C45DF9E3ECB-2zbAqoMm/rLQX//ci7WS+53eMK7GYZcrXYFosVITYPE@public.gmane.org>
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=3485100.RiP6AQCKWQ@x220 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=xingbow-vV1OtcyAfmbQT0dZR+AlfA@public.gmane.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).