From: Alexander Duyck <alexander.h.duyck@intel.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jeffrey.t.kirsher@intel.com,
edumazet@google.com, bhutchings@solarflare.com,
therbert@google.com, alexander.duyck@gmail.com
Subject: [RFC PATCH 0/2] Coalesce MMIO writes for transmits
Date: Wed, 11 Jul 2012 17:25:58 -0700 [thread overview]
Message-ID: <20120712002103.27846.73812.stgit@gitlad.jf.intel.com> (raw)
This patch set is meant to address recent issues I found with ixgbe
performance being bound by Tx tail writes. With these changes in place
and the dispatch_limit set to 1 or more I see a significant increase in
performance.
In the case of one of my systems I saw the routing rate for 7 queues jump
from 10.5 to 11.7Mpps. The overall increase I have seen on most systems is
something on the order of about 15%. In the case of pktgen I have also
seen a noticeable increase as the previous limit for transmits was
~12.5Mpps, but with this patch set in place and the dispatch_limit enabled
the value increases to ~14.2Mpps.
I expected there to be an increase in latency, however so far I have not
ran into that. I have tried running NPtcp tests for latency and seen no
difference in the coalesced and non-coalesced transaction times. I welcome
any suggestions for tests I might run that might expose any latency issues
as a result of this patch.
---
Alexander Duyck (2):
ixgbe: Add functionality for delaying the MMIO write for Tx
net: Add new network device function to allow for MMIO batching
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 22 +++++++-
include/linux/netdevice.h | 57 +++++++++++++++++++++
net/core/dev.c | 67 +++++++++++++++++++++++++
net/core/net-sysfs.c | 36 +++++++++++++
4 files changed, 180 insertions(+), 2 deletions(-)
--
Thanks,
Alex
next reply other threads:[~2012-07-12 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 0:25 Alexander Duyck [this message]
2012-07-12 0:26 ` [RFC PATCH 1/2] net: Add new network device function to allow for MMIO batching Alexander Duyck
2012-07-12 7:14 ` Eric Dumazet
2012-07-12 15:39 ` Alexander Duyck
2012-07-13 7:38 ` Eric Dumazet
2012-07-13 15:37 ` Alexander Duyck
2012-07-13 15:50 ` Stephen Hemminger
2012-07-13 16:23 ` Eric Dumazet
2012-07-13 7:19 ` Eric Dumazet
2012-07-13 15:49 ` Alexander Duyck
2012-07-13 16:18 ` Eric Dumazet
2012-07-12 0:26 ` [RFC PATCH 2/2] ixgbe: Add functionality for delaying the MMIO write for Tx Alexander Duyck
2012-07-12 17:23 ` [RFC PATCH 0/2] Coalesce MMIO writes for transmits Stephen Hemminger
2012-07-12 19:01 ` Alexander Duyck
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=20120712002103.27846.73812.stgit@gitlad.jf.intel.com \
--to=alexander.h.duyck@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).