All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Quan Xu <quan.xu@intel.com>, Yang Z Zhang <yang.z.zhang@intel.com>
Cc: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	Kevin Tian <kevin.tian@intel.com>,
	DonaldD Dugger <donald.d.dugger@intel.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: VT-d async invalidation for Device-TLB.
Date: Tue, 16 Jun 2015 08:57:08 +0100	[thread overview]
Message-ID: <557FF2F4020000780008544A@mail.emea.novell.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28890E92C2C9@SHSMSX101.ccr.corp.intel.com>

>>> On 16.06.15 at 05:55, <quan.xu@intel.com> 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, <quan.xu@intel.com> wrote:
>> >>> On 12.06.15 at 14:47, <JBeulich@suse.com> wrote:
>> >>>>>> On 12.06.15 at 04:40, <quan.xu@intel.com> wrote:
>> >>>> I tested it by a Myri-10G Dual-Protocol NIC, which is an ATS device.
>> >>>> for an invalidation:
>> >>>>  By sync way, it takes about 1.4 ms.
>> >>>>  By async way, it takes about 4.3 ms.
>> 
>> It is a typo for the time: should be 1.4 us and 4.3 us.
>> 
> 
> yes, it is 1.4 us and 4.3 us.
> Thanks.
> 
> I also have tested iotlb sync and async invalidation.
> For sync way: it takes about 3.2 us.
> For async way: it takes about 5.3 us.

That's _longer_ than in the ATS case. Is that realistic?

Jan

  reply	other threads:[~2015-06-16  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16  3:55 VT-d async invalidation for Device-TLB Xu, Quan
2015-06-16  7:57 ` Jan Beulich [this message]
2015-06-16  8:29   ` Xu, Quan
  -- strict thread matches above, loose matches on Subject: below --
2015-06-03  7:49 Xu, Quan
2015-06-10  8:04 ` Jan Beulich
2015-06-12  2:40   ` Xu, Quan
2015-06-12  6:46     ` Jan Beulich

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=557FF2F4020000780008544A@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=donald.d.dugger@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=quan.xu@intel.com \
    --cc=xen-devel@lists.xenproject.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.