All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org, users@dpdk.org, qemu-devel@nongnu.org,
	qemu-discuss@nongnu.org
Subject: Re: Will huge page have negative effect on guest vm in qemu enviroment?
Date: Wed, 21 Jun 2017 11:35:56 +0800	[thread overview]
Message-ID: <CAOE=1Z1LJr9rpaEQ9+b7D5vM3N=Wy0oGunRnzoQ79x3dWA3oaw@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z1Bbgb494m6mYRnX1-80eT0tSnF0F6zNM7efEie4rd7DA@mail.gmail.com>

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 <batmanustc@gmail.com>:

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

WARNING: multiple messages have this Message-ID (diff)
From: Sam <batmanustc@gmail.com>
To: dev@dpdk.org, users@dpdk.org, qemu-devel@nongnu.org,
	qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] Will huge page have negative effect on guest vm in qemu enviroment?
Date: Wed, 21 Jun 2017 11:35:56 +0800	[thread overview]
Message-ID: <CAOE=1Z1LJr9rpaEQ9+b7D5vM3N=Wy0oGunRnzoQ79x3dWA3oaw@mail.gmail.com> (raw)
In-Reply-To: <CAOE=1Z1Bbgb494m6mYRnX1-80eT0tSnF0F6zNM7efEie4rd7DA@mail.gmail.com>

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 <batmanustc@gmail.com>:

> 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	other threads:[~2017-06-21  3:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  3:32 Will huge page have negative effect on guest vm in qemu enviroment? Sam
2017-06-21  3:32 ` [Qemu-devel] " Sam
2017-06-21  3:35 ` Sam [this message]
2017-06-21  3:35   ` Sam
2017-06-21  6:15   ` Pavel Shirshov
2017-06-21  6:15     ` [Qemu-devel] [dpdk-dev] " Pavel Shirshov
2017-06-21  7:22     ` Sam
2017-06-21  7:22       ` [Qemu-devel] [dpdk-dev] " Sam
2017-06-21  9:03       ` Gaëtan Rivet
2017-06-21 19:16       ` [Qemu-devel] " Dr. David Alan Gilbert
2017-06-21 19:16         ` [Qemu-devel] [dpdk-dev] " Dr. David Alan Gilbert
2017-06-21 19:35         ` Chris Friesen
2017-06-22  9:24       ` Alejandro Lucero
2017-06-22  9:24         ` [Qemu-devel] [dpdk-dev] " Alejandro Lucero

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='CAOE=1Z1LJr9rpaEQ9+b7D5vM3N=Wy0oGunRnzoQ79x3dWA3oaw@mail.gmail.com' \
    --to=batmanustc@gmail.com \
    --cc=dev@dpdk.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=users@dpdk.org \
    /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.