linux-kernel - Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33

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: <4B2F978D.7010602@redhat.com>
Date:	Mon, 21 Dec 2009 17:43:09 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Gregory Haskins <gregory.haskins@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, kvm@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org,
	"alacrityvm-devel@...ts.sourceforge.net" 
	<alacrityvm-devel@...ts.sourceforge.net>
Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33

On 12/21/2009 05:34 PM, Gregory Haskins wrote:
>
>> I think it would be fair to point out that these patches have been objected to
>> by the KVM folks quite extensively,
>>      
> Actually, these patches have nothing to do with the KVM folks.  You are
> perhaps confusing this with the hypervisor-side discussion, of which
> there is indeed much disagreement.
>    

This is true, though these drivers are fairly pointless for 
virtualization without the host side support.

I did have a few issues with the guest drivers:
- the duplication of effort wrt virtio.  These drivers don't cover 
exactly the same problem space, but nearly so.
- no effort at scalability - all interrupts are taken on one cpu
- the patches introduce a new virtual interrupt controller for dubious 
(IMO) benefits

>  From my research, the reason why virt in general, and KVM in particular
> suffers on the IO performance front is as follows: IOs
> (traps+interrupts) are more expensive than bare-metal, and real hardware
> is naturally concurrent (your hbas and nics are effectively parallel
> execution engines, etc).
>
> Assuming my observations are correct, in order to squeeze maximum
> performance from a given guest, you need to do three things:  A)
> eliminate as many IOs as you possibly can, B) reduce the cost of the
> ones you can't avoid, and C) run your algorithms in parallel to emulate
> concurrent silicon.
>    

All these are addressed by vhost-net without introducing new drivers.

-- 
error compiling committee.c: too many arguments to function

--
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/