From: Shaohua Li <shli@fb.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: <linux-kernel@vger.kernel.org>, <gang.wei@intel.com>,
<hpa@linux.intel.com>, <mingo@kernel.org>, <kernel-team@fb.com>,
<ning.sun@intel.com>, <srihan@fb.com>, <alex.eydelberg@intel.com>
Subject: Re: [RFC] x86/tboot: add an option to disable iommu force on
Date: Mon, 3 Apr 2017 12:19:28 -0700 [thread overview]
Message-ID: <20170403191927.GA35817@MacBook-Pro.local> (raw)
In-Reply-To: <20170322115055.GA35752@dhcp-172-20-162-56.dhcp.thefacebook.com>
On Wed, Mar 22, 2017 at 07:50:55AM -0400, Shaohua Li wrote:
> On Wed, Mar 22, 2017 at 11:49:00AM +0100, Joerg Roedel wrote:
> > Hi Shaohua,
> >
> > On Tue, Mar 21, 2017 at 11:37:51AM -0700, Shaohua Li wrote:
> > > IOMMU harms performance signficantly when we run very fast networking
> > > workloads. This is a limitation in hardware based on our observation, so
> > > we'd like to disable the IOMMU force on, but we do want to use TBOOT and
> > > we can sacrifice the DMA security bought by IOMMU. I must admit I know
> > > nothing about TBOOT, but TBOOT guys (cc-ed) think not eabling IOMMU is
> > > totally ok.
> >
> > Can you elaborate a bit more on the setup where the IOMMU still harms
> > network performance? With the recent scalability improvements I measured
> > only a minimal impact on 10GBit networking.
> Hi,
>
> It's 40GB networking doing XDP test. Software overhead is almost unaware, but
> it's the IOTLB miss (based on our analysis) which kills the performance. We
> observed the same performance issue even with software passthrough (identity
> mapping), only the hardware passthrough survives. The pps with iommu (with
> software passthrough) is only about ~30% of that without it.
Hi,
Any update on this?
Thanks,
Shaohua
next prev parent reply other threads:[~2017-04-03 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 18:37 [RFC] x86/tboot: add an option to disable iommu force on Shaohua Li
2017-03-22 10:49 ` Joerg Roedel
2017-03-22 11:50 ` Shaohua Li
2017-04-03 19:19 ` Shaohua Li [this message]
2017-04-07 10:08 ` Joerg Roedel
2017-04-07 21:49 ` Sun, Ning
2017-04-10 4:31 ` Shaohua Li
2017-04-10 21:28 ` Sun, Ning
2017-04-24 16:50 ` Shaohua Li
2017-04-25 11:02 ` Joerg Roedel
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=20170403191927.GA35817@MacBook-Pro.local \
--to=shli@fb.com \
--cc=alex.eydelberg@intel.com \
--cc=gang.wei@intel.com \
--cc=hpa@linux.intel.com \
--cc=jroedel@suse.de \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ning.sun@intel.com \
--cc=srihan@fb.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.