All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Su, David W" <david.w.su@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] igb_uio: use non-threaded ISR
Date: Sat, 25 Feb 2017 00:21:22 +0000	[thread overview]
Message-ID: <3875C02542CA2945BF761013C1F5B8E57F3E7953@ORSMSX109.amr.corp.intel.com> (raw)
In-Reply-To: <22f235a0-d991-d4b0-b72d-1a2a3d5bfa82@intel.com>

>-----Original Message-----
>From: Yigit, Ferruh
>Sent: Friday, February 24, 2017 9:55 AM
>To: Su, David W <david.w.su@intel.com>; dev@dpdk.org
>Subject: Re: [dpdk-dev] [PATCH] igb_uio: use non-threaded ISR
>
>On 1/20/2017 11:08 PM, David Su wrote:
>> This eliminates the overhead of a task switch when an interrupt arrives.
>
>Hi David,
>
>Did you test patch with l3fwd-power (or any app that uses Rx
>interrupts), is there any performance gain?
>
Hi Ferruh,

The test is a simple l2 forward app and it uses the same idle heuristic as l3fwd-power, i.e. it enables rx interrupts and goes to sleep after about 300us without receiving a packet.  A packet generator is configured to send a time stamped packet every 400us to ensure the test will go through the sleep-wakeup cycle with every inbound packet.  The packet generator measures packet round trip latency with the timestamps.

The average latency is more than 100us on a 2.30GHz Xeon E5-2699 v3 platform with Intel X540-AT2 NIC.  The long latency is mostly because the DPDK ixgbe driver enables interrupt throttling in the NIC and sets the minimum inter-interrupt interval to about 500us.  With this patch alone, there is no significant change to the average latency, the maximum latency is reduced from 418us to 392us.  If interrupt throttling is not enabled (http://dpdk.org/dev/patchwork/patch/19856/), the average latency is reduced from 17us to 14us and the maximum latency from 30us to 21us.

>>
>> Signed-off-by: David Su <david.w.su@intel.com>
><...>

  reply	other threads:[~2017-02-25  0:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 23:08 [PATCH] igb_uio: use non-threaded ISR David Su
2017-01-20 23:50 ` Stephen Hemminger
2017-01-23 19:20   ` Su, David W
2017-01-23 21:12     ` Stephen Hemminger
2017-02-24 17:54 ` Ferruh Yigit
2017-02-25  0:21   ` Su, David W [this message]
2017-02-27 16:15 ` Ferruh Yigit
2017-03-30 20:28   ` Thomas Monjalon

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=3875C02542CA2945BF761013C1F5B8E57F3E7953@ORSMSX109.amr.corp.intel.com \
    --to=david.w.su@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.