public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed

From: Jason Wang <jasowang@redhat•com>
To: "Michael S. Tsirkin" <mst@redhat•com>
Cc: aarcange@redhat•com, Christoph Hellwig <hch@infradead•org>,
	linux-parisc@vger•kernel.org, kvm@vger•kernel.org,
	netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
	virtualization@lists•linux-foundation.org,
	James Bottomley <James.Bottomley@hansenpartnership•com>,
	linux-mm@kvack•org, jglisse@redhat•com, jgg@mellanox•com,
	David Miller <davem@davemloft•net>,
	linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 2/2] vhost: re-introducing metadata acceleration through kernel virtual address
Date: Mon, 9 Sep 2019 10:30:20 +0800	[thread overview]
Message-ID: <868bfaed-ede4-6da8-0247-af2a03ea121d@redhat.com> (raw)
In-Reply-To: <1cb5aa8d-6213-5fce-5a77-fcada572c882@redhat.com>


On 2019/9/9 上午10:18, Jason Wang wrote:
>>>
>>> On a elder CPU Sandy Bridge without SMAP support. TX PPS doesn't see
>>> any difference.
>> Why is not Kaby Lake with SMAP off the same as Sandy Bridge?
>
>
> I don't know, I guess it was because the atomic is l 


Sorry, I meant atomic costs less for Kaby Lake.

Thanks



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

next prev parent reply	other threads:[~2019-09-09  2:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190905122736.19768-1-jasowang@redhat.com>
2019-09-05 12:27 ` [PATCH 2/2] vhost: re-introducing metadata acceleration through kernel virtual address Jason Wang
2019-09-08 11:05   ` Michael S. Tsirkin
2019-09-09  2:18     ` Jason Wang
2019-09-09  2:30       ` Jason Wang [this message]
2019-09-09  4:45       ` Michael S. Tsirkin
2019-09-09  7:23         ` Jason Wang
2019-09-06  3:21 ` Hillf Danton
2019-09-06 12:51   ` Jason Wang

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=868bfaed-ede4-6da8-0247-af2a03ea121d@redhat.com \
    --to=jasowang@redhat$(echo .)com \
    --cc=James.Bottomley@hansenpartnership$(echo .)com \
    --cc=aarcange@redhat$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=hch@infradead$(echo .)org \
    --cc=jgg@mellanox$(echo .)com \
    --cc=jglisse@redhat$(echo .)com \
    --cc=kvm@vger$(echo .)kernel.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-parisc@vger$(echo .)kernel.org \
    --cc=mst@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=virtualization@lists$(echo .)linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox