All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: ixgbe/linux/sparc perf issues
Date: Thu, 11 Dec 2014 20:21:00 +0000	[thread overview]
Message-ID: <20141211202100.GD5536@oracle.com> (raw)
In-Reply-To: <20141211194542.GA5536@oracle.com>

On (12/11/14 15:09), David Miller wrote:
> 
> The real overhead is unavoidable due to the way the hypervisor access
> to the IOMMU is implemented in sun4v.
> 
> If we had direct access to the hardware, we could avoid all of the
> real overhead in %99 of all IOMMU mappings, as we do for pre-sun4v
> systems.
> 
> On sun4u systems, we never flush the IOMMU until we wrap around
> the end of the IOMMU arena to the beginning in order to service
> an allocation.
> 
> Such an optimization is impossible with the hypervisor call interface
> in sun4v.
> 
> I've known about this issue for a decade and I do not think there is
> anything we can really do about this.

All this may be true, but it would also be true for Solaris, which
manages to do line-speed (for the exact same setup), so there must be
some other bottleneck going on? 

And fwiw, removing the iommu lock contention out of lockstat
did not make any difference to the throughput, which seems to indicate
that the bottleneck is elsewhere. Hence the question about the
ixgbe stats, and tuning that I may be missing.

--Sowmini


  parent reply	other threads:[~2014-12-11 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 19:45 ixgbe/linux/sparc perf issues Sowmini Varadhan
2014-12-11 20:09 ` David Miller
2014-12-11 20:21 ` Sowmini Varadhan [this message]
2014-12-11 20:24 ` David Miller
2014-12-11 20:27 ` David Miller
2014-12-12 16:16 ` Sowmini Varadhan
2014-12-19 15:11 ` Sowmini Varadhan
2014-12-19 17:10 ` David Miller

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=20141211202100.GD5536@oracle.com \
    --to=sowmini.varadhan@oracle.com \
    --cc=sparclinux@vger.kernel.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 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.