All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Anshul Makkar anshul.makkar"@citrix.com, xen-devel@lists.xen.org
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com,
	anshulma <anshul.makkar@citrix.com>,
	jbeulich@suse.com
Subject: Re: [PATCH] iommu/quirk: disable shared EPT for Sandybridge and earlier processors.
Date: Fri, 28 Aug 2015 17:24:25 +0100	[thread overview]
Message-ID: <55E08B39.5070300@citrix.com> (raw)
In-Reply-To: <1440776507-30218-1-git-send-email-anshul.makkar@citrix.com>

On 28/08/15 16:41, "Anshul Makkar anshul.makkar"@citrix.com wrote:
> From: anshulma <anshul.makkar@citrix.com>
>
> Sandybridge or earlier processors don't have huge page support for
> IOTLB which leads to fallback on 4k pages and causes performance issues.
>
> Shared EPT will be disabled only if the user has not provided explicit
> choice on the command line.
>
> Signed-off-by: Anshul Makkar <anshul.makkar@citrix.com>

As a note concerning the performance issues, for some IO workloads, this
nets a 40% throughput improvement.

We did not observe any IO workloads which had a worse performance as a
result of disabling shared ept.

Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

~Andrew

       reply	other threads:[~2015-08-28 16:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1440776507-30218-1-git-send-email-anshul.makkar@citrix.com>
2015-08-28 16:24 ` Andrew Cooper [this message]
2015-08-31  8:09 ` [PATCH] iommu/quirk: disable shared EPT for Sandybridge and earlier processors Jan Beulich
2015-09-01 14:18   ` Andrew Cooper
2015-09-01 14:55     ` Jan Beulich
2015-11-24 17:17 Anshul
2015-11-24 17:41 ` Jan Beulich
2015-11-25 10:28   ` Andrew Cooper
2015-11-25 10:49     ` Jan Beulich
2015-11-25 15:13       ` Andrew Cooper
2015-11-25 15:38         ` Jan Beulich
2015-11-25 15:58           ` Malcolm Crossley
2015-11-26  7:17             ` Tian, Kevin
2015-12-01 16:45               ` Anshul Makkar
2015-12-01 17:20                 ` Jan Beulich
2015-11-26  8:45             ` Jan Beulich
2015-11-26 10:27               ` Andrew Cooper
2015-11-26 10:39                 ` Jan Beulich
2015-11-26 11:42                   ` Andrew Cooper
2015-11-26 11:53                     ` Jan Beulich
2015-11-26 13:46     ` Jan Beulich
2015-11-26 13:48       ` Malcolm Crossley
2015-11-26 13:55         ` Andrew Cooper
2015-11-30 21:22           ` Konrad Rzeszutek Wilk
2015-12-01 10:34             ` Andrew Cooper
2015-12-01 10:44               ` Anshul Makkar
2015-12-01 15:24               ` Konrad Rzeszutek Wilk
2015-12-01 16:19                 ` Andrew Cooper
2015-12-03  1:19           ` Tian, Kevin
2015-12-03 11:24             ` Andrew Cooper
2015-12-04  1:55               ` Tian, Kevin
2015-12-03  2:40           ` Tian, Kevin
2015-12-03  8:18             ` Jan Beulich
2015-12-03  8:50               ` Tian, Kevin
2015-12-03 11:19                 ` Andrew Cooper
2015-12-04  2:35                   ` Tian, Kevin

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=55E08B39.5070300@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc="Anshul Makkar anshul.makkar"@citrix.com \
    --cc=anshul.makkar@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=kevin.tian@intel.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@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.