netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: davem@davemloft.net, sowmini.varadhan@oracle.com,
	raghuram.kothakota@oracle.com
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] sunvnet: Reduce LDC message overhead.
Date: Fri, 29 Aug 2014 16:16:24 -0400	[thread overview]
Message-ID: <20140829201624.GG14753@oracle.com> (raw)


This patch series has 2 sets of changes to reduce the overhead
from LDC messages.

- the current linux sunvnet driver sends out many more LDC start and stop
  triggers than it needs to: when we are sending a burst of packets across
  multiple descriptor rings, we only need to send the "start" trigger for
  the first dring (we currently send one for every dring). And we only need
  to send the "STOPPED" trigger for the last dring (and if that fails, hold
  off and send the trigger later).

- When reading the descriptor rings, don't give up as soon as a dring
  that is not VIO_DESC_READY is found- especially when the peer is sending
  a burst of packets, it is worthwhile to recheck the descriptor status
  after a small microsecond delay, as the likelihood of finding this
  descriptor READY is high, and it is cheaper to just retry with a delay
  than to return from the current context, read another LDC message,
  and then come back to read this descriptor.

Sowmini Varadhan (2):
  Avoid sending superfluous LDC messages.
  Re-check for a VIO_DESC_READY data descriptor after short udelay()

 drivers/net/ethernet/sun/sunvnet.c | 87 ++++++++++++++++++++++++++++++++++----
 drivers/net/ethernet/sun/sunvnet.h |  4 ++
 2 files changed, 83 insertions(+), 8 deletions(-)

-- 
1.8.4.2

                 reply	other threads:[~2014-08-29 20:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140829201624.GG14753@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=raghuram.kothakota@oracle.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).