[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] [dpdk-dev] Will huge page have negative effect on gue

From: Sam
Subject: Re: [Qemu-discuss] [dpdk-dev] Will huge page have negative effect on guest vm in qemu enviroment?
Date: Wed, 21 Jun 2017 15:22:45 +0800

Thank you~

1. We have a compare test on qemu-kvm enviroment with huge page and without
huge page. Qemu start process is much longer in huge page enviromwnt. And I
write an email titled with '[DPDK-memory] how qemu waste such long time
under dpdk huge page envriment?'. I could resend it later.

2. Then I have another test on qemu-kvm enviroment with huge page and
without huge page, which I didn't start ovs-dpdk and vhostuser port in qemu
start process. And I found Qemu start process is also much longer in huge
page enviroment.

So I think huge page enviroment, which grub2.cfg file is specified in
how qemu waste such long time under dpdk huge page envriment?’, will really
have negative effect on qemu start up process.

That's why we don't like to use ovs-dpdk. Althrough ovs-dpdk is faster, but
the start up process of qemu is much longer then normal ovs, and the reason
is nothing with ovs but huge page. For customers, vm start up time is
important then network speed.

BTW, ovs-dpdk start up process is also longer then normal ovs. But I know
the reason, it's dpdk EAL init process with forking big continous memory
and zero this memory. For qemu, I don't know why, as there is no log to
report this.

2017-06-21 14:15 GMT+08:00 Pavel Shirshov <address@hidden>:

> Hi Sam,
> Below I'm saying about KVM. I don't have experience with vbox and others.
> 1. I'd suggest don't use dpdk inside of VM if you want to see best
> perfomance on the box.
> 2. huge pages enabled globally will not have any bad effect to guest
> OS. Except you have to enable huge pages inside of VM and provide real
> huge page for VM's huge pages from the host system. Otherwise dpdk
> will use "hugepages" inside of VM, but this "huge pages" will not real
> ones. They will be constructed from normal pages outside. Also when
> you enable huge pages OS will reserve them from start and your OS will
> not able use them for other things. Also you can't swap out huge
> pages, KSM will not work for them and so on.
> 3. You can enable huge pages just for one numa node. It's impossible
> to enable them just for one core. Usually you reserve some memory for
> hugepages when the system starts and you can't use this memory in
> normal applications unless normal application knows how to use them.
> Also why it didn't work inside of the docker?
> On Tue, Jun 20, 2017 at 8:35 PM, Sam <address@hidden> wrote:
> > BTW, we also think about use ovs-dpdk in docker enviroment, but test
> result
> > said it's not good idea, we don't know why.
> >
> > 2017-06-21 11:32 GMT+08:00 Sam <address@hidden>:
> >
> >> Hi all,
> >>
> >> We plan to use DPDK on HP host machine with several core and big memory.
> >> We plan to use qemu-kvm enviroment. The host will carry 4 or more guest
> vm
> >> and 1 ovs.
> >>
> >> Ovs-dpdk is much faster then normal ovs, but to use ovs-dpdk, we have to
> >> enable huge page globally.
> >>
> >> My question is, will huge page enabled globally have negative effect on
> >> guest vm's memory orperate or something? If it is, how to prevent this,
> or
> >> could I enable huge page on some core or enable huge page for a part of
> >> memory?
> >>
> >> Thank you~
> >>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]