All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitesh Narayan Lal <nilal@redhat.com>
To: Rik van Riel <riel@redhat.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com, pagupta@redhat.com,
	wei.w.wang@intel.com, yang.zhang.wz@gmail.com, david@redhat.com,
	mst@redhat.com, dodgen@google.com, konrad.wilk@oracle.com
Subject: Re: [Patch v4 0/6] KVM: Guest page hinting
Date: Mon, 13 Nov 2017 10:14:21 -0500	[thread overview]
Message-ID: <44024129-6928-bb07-e11b-886991e6528e@redhat.com> (raw)
In-Reply-To: <1510521836.21121.273.camel@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1276 bytes --]

Hi Rik,


On 11/12/2017 04:23 PM, Rik van Riel wrote:
> On Fri, 2017-11-03 at 16:30 -0400, nilal@redhat.com wrote:
>> The following patch-set proposes an efficient mechanism for handing
>> freed memory between the guest and the host. It enables the guests
>> with DAX (no page cache) to rapidly free and reclaim memory to and
>> from the host respectively. 
>
>> Performance:
>> 	Test criteria: Kernel Build
>> 	Command: make clean;make defconfig;time make
>> 	With Hinting:
>> 		real: 21m24.680s
>> 		user: 16m3.362s
>> 		sys : 2m19.027s
>> 	Without Hinting:
>> 		real: 21m18.062s
>> 		user: 16m13.969s
>> 		sys : 1m17.884s
>>
>> 	Test criteria: Stress Test
>> 	Command: time stress --io 2 --cpu 2 --vm 2 --vm-bytes 1024M --
>> timeout 100s -v
>> 	With Hinting:
>> 		real: 1m40.726s
>> 		user: 1m23.449s
>> 		sys : 0m5.576s
>> 	Without Hinting:
>> 		real: 1m40.378s
>> 		user: 1m21.292s
>> 		sys : 0m4.972s
> These numbers look really good, but these workloads are mostly in
> user space.
>
> Could you also try with more kernel heavy workloads, like netperf
> (sender and receiver on the same CPU, vs sender and receiver on
> different CPUs) and hackbench?
>
Yeap, I can do that. Thanks for the suggestion.

-- 
Regards
Nitesh


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2017-11-13 15:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 20:30 [Patch v4 0/6] KVM: Guest page hinting nilal
2017-11-03 20:30 ` [Patch v4 1/6] KVM: Support for guest " nilal
2017-11-13 17:59   ` Michael S. Tsirkin
2017-11-15 19:38     ` Nitesh Narayan Lal
2017-11-15 20:06       ` Michael S. Tsirkin
2017-11-03 20:30 ` [Patch v4 2/6] KVM: Guest page hinting functionality nilal
2017-11-13 18:03   ` Michael S. Tsirkin
2017-11-03 20:30 ` [Patch v4 3/6] KVM: Adding tracepoints for guest page hinting nilal
2017-11-03 20:30 ` [Patch v4 4/6] virtio: Exposes added descriptor to the other side synchronously nilal
2017-11-03 20:30 ` [Patch v4 5/6] KVM: Sending hyperlist to the host via hinting_vq nilal
2017-11-03 20:30 ` [Patch v4 6/6] KVM: Enabling guest page hinting via static key nilal
2017-11-03 20:37 ` [QEMU PATCH] kvm: Support for guest page hinting nilal
2017-11-03 20:37   ` nilal
2017-11-06 11:21     ` Pankaj Gupta
2017-11-06 14:21       ` Nitesh Narayan Lal
2017-11-12 21:23 ` [Patch v4 0/6] KVM: Guest " Rik van Riel
2017-11-13 15:14   ` Nitesh Narayan Lal [this message]

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=44024129-6928-bb07-e11b-886991e6528e@redhat.com \
    --to=nilal@redhat.com \
    --cc=david@redhat.com \
    --cc=dodgen@google.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pagupta@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=riel@redhat.com \
    --cc=wei.w.wang@intel.com \
    --cc=yang.zhang.wz@gmail.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.