> June 16, 2015 3:57 PM wrote:
> >>> On 16.06.15 at 05:55, wrote:
> >> From: Zhang, Yang wrote on June 16, 2015 11:07 AM
> >>> Jan Beulich wrote on 2015-06-15:
> >> On 13.06.15 at 16:44, wrote:
> >> >>> On 12.06.15 at 14:47, wrote:
> >> >> On 12.06.15 at 04:40, wrote:
> >> I tes
>>> On 16.06.15 at 05:55, wrote:
>> From: Zhang, Yang wrote on June 16, 2015 11:07 AM
>>> Jan Beulich wrote on 2015-06-15:
>> On 13.06.15 at 16:44, wrote:
>> >>> On 12.06.15 at 14:47, wrote:
>> >> On 12.06.15 at 04:40, wrote:
>> I tested it by a Myri-10G Dual-Protocol NIC, which
> From: Zhang, Yang wrote on June 16, 2015 11:07 AM
>> Jan Beulich wrote on 2015-06-15:
> On 13.06.15 at 16:44, wrote:
> >>> On 12.06.15 at 14:47, wrote:
> >> On 12.06.15 at 04:40, wrote:
> > On 10.06.15 at 16:05, wrote:
> On 03.06.15 at 09:49, wrote:
> >> For
>>> On 12.06.15 at 04:40, wrote:
>> > >>> On 10.06.15 at 16:05, wrote:
>> >>> On 03.06.15 at 09:49, wrote:
>> > For Context Invalidation and IOTLB invalidation without Device-TLB
>> > invalidation, Invalidation Queue flushes synchronous invalidation as
>> > before(This is a tradeoff and the
>> >>> On 10.06.15 at 16:05, wrote:
> >>> On 03.06.15 at 09:49, wrote:
Jan, thanks for your review!!
> > Design Overview
> > =
> > This design implements a non-spinning model for Device-TLB
> > invalidation - using an interrupt based mechanism. Each domain
> > maintains a invalidati
>>> On 03.06.15 at 09:49, wrote:
> Design Overview
> =
> This design implements a non-spinning model for Device-TLB invalidation -
> using
> an interrupt based mechanism. Each domain maintains a invalidation table, and
> the hypervisor has an entry of invalidation tables. The invali
Hi All,
This Email is about VT-d async invalidation for Device-TLB.
Background
=
As Jan Beulich
mentioned(http://lists.xenproject.org/archives/html/xen-devel/2014-06/msg03351.html
), VT-d code currently has a number of cases where completion of certain
operations is being waited f
