linux-kernel - Re: [PATCH 0/5] kvm: memslots lookup optimization

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <547CA79A.10206@redhat.com>
Date:	Mon, 01 Dec 2014 18:38:34 +0100
From:	Paolo Bonzini <pbonzini@...hat.com>
To:	Igor Mammedov <imammedo@...hat.com>, linux-kernel@...r.kernel.org
CC:	kvm@...r.kernel.org
Subject: Re: [PATCH 0/5] kvm: memslots lookup optimization



On 01/12/2014 18:29, Igor Mammedov wrote:
> Series speed-ups GFN to memslot lookup time by:
>  * introducing LRU cache, which improves looukup time for
>    same slot workload (typically boot time of Windows and Linux guest)
>  * switching to binary search for GFN to memslot lookup,
>    improving lookup time with large amount of memory slots
> 
> Igor Mammedov (5):
>   kvm: update_memslots: drop not needed check for the same number of
>     pages
>   kvm: update_memslots: drop not needed check for the same slot
>   kvm: search_memslots: add simple LRU memslot caching
>   kvm: change memslot sorting rule from size to GFN
>   kvm: optimize GFN to memslot lookup with large slots amount
> 
>  include/linux/kvm_host.h | 28 +++++++++++++++++++++++-----
>  virt/kvm/kvm_main.c      | 46 ++++++++++++++++++++++++++--------------------
>  2 files changed, 49 insertions(+), 25 deletions(-)
> 

Applied patches 1-3 for now, I'm not in the mood for proving that the
binary search is correct. :)

Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/