From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: Tim Deegan <tim@xen.org>
Cc: "xiantao.zhang@intel.com" <xiantao.zhang@intel.com>,
Santosh Jodh <Santosh.Jodh@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Superpages for VT-D
Date: Fri, 20 Jul 2012 14:38:02 -0700 [thread overview]
Message-ID: <CAL54oT3yqLtDpEHe7n20K=i-hz27P-TYK11tm+VNL2BXMs+hMg@mail.gmail.com> (raw)
In-Reply-To: <20120719145318.GA78502@ocelot.phlegethon.org>
[-- Attachment #1.1: Type: text/plain, Size: 751 bytes --]
On Thu, Jul 19, 2012 at 7:53 AM, Tim Deegan <tim@xen.org> wrote:
> At 07:01 -0700 on 19 Jul (1342681270), Santosh Jodh wrote:
> > I understand the value of using superpages for IOMMU. What are the
> > other advantages of sharing the table between the MMU and IOMMU (other
> > than saving table memory)?
>
> It's mostly the memory, but also it's faster to update one table than
> two, and we don't have to worry about them getting out of sync with each
> other. I don't think there are any deeper reasons.
>
> Cheers,
>
> Tim.
>
>
- The code can be simpler because you don't need to maintain the same info
"guest physical -> host physical" in two different places.
- Maybe cache utilization can be better
--
Jun
Intel Open Source Technology Center
[-- Attachment #1.2: Type: text/html, Size: 1182 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-07-20 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 16:18 Superpages for VT-D Santosh Jodh
2012-07-19 10:23 ` Tim Deegan
2012-07-19 14:01 ` Santosh Jodh
2012-07-19 14:53 ` Tim Deegan
2012-07-20 21:38 ` Nakajima, Jun [this message]
2012-07-23 17:56 ` Santosh Jodh
2012-07-24 19:41 ` Tim Deegan
2012-07-31 20:44 ` Santosh Jodh
2012-08-02 11:11 ` Tim Deegan
2012-08-02 15:56 ` Santosh Jodh
2012-08-03 11:40 ` Tim Deegan
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='CAL54oT3yqLtDpEHe7n20K=i-hz27P-TYK11tm+VNL2BXMs+hMg@mail.gmail.com' \
--to=jun.nakajima@intel.com \
--cc=Santosh.Jodh@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.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.