From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: "Kay, Allen M" <allen.m.kay@intel.com>,
Chris Wright <chrisw@sous-sol.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"matthew@wil.cx" <matthew@wil.cx>
Subject: Re: [PATCH ACS v3 1/1]
Date: Mon, 5 Oct 2009 17:14:19 -0700 [thread overview]
Message-ID: <20091005171419.5464502d@jbarnes-g45> (raw)
In-Reply-To: <20091001011721.GK3958@sequoia.sous-sol.org>
On Wed, 30 Sep 2009 18:17:21 -0700
Chris Wright <chrisw@sous-sol.org> wrote:
> * Kay, Allen M (allen.m.kay@intel.com) wrote:
> > On the other hand, can we say VT-d PT mode is mainly for KVM
> > virtualization use case? If so, is it reasonable to say
> > performance of host P2P in this mode is not of highest priority?
>
> Guess it depends on the workload. Would be helpful to identify a use
> case that is p2p heavy (and then the impact of enabling ACS).
>
> > If not, another option is to have a kernel boot parameter to
> > configure an kernel boot instance to be either host kernel
> > optimized or virtualization optimized. I don't know whether this
> > is a reasonable or not ...
>
> I was thinking that ACS could be enabled if an IOMMU is enabled. Not
> a perfect fit, but seems reasonably close.
Allen, did you want to do these changes as an incremental patch on your
last one or just send me a replacement? Either way is fine with me.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-10-06 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 23:46 Allen Kay
2009-09-29 0:00 ` Chris Wright
2009-09-29 17:46 ` Kay, Allen M
2009-09-29 18:46 ` Chris Wright
2009-09-30 23:33 ` Kay, Allen M
2009-10-01 1:17 ` Chris Wright
2009-10-06 0:14 ` Jesse Barnes [this message]
2009-10-06 0:29 ` Kay, Allen M
2009-10-06 20:15 ` Kay, Allen M
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=20091005171419.5464502d@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=allen.m.kay@intel.com \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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
all inboxes | Powered by JetHome®