From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Yuanhan Liu <yliu@fridaylinux.org>,
"Wang, Wei 5. (NSB - CN/Hangzhou)" <wei.5.wang@nokia-sbell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] The limitation of VHOST_MEMORY_MAX_NREGIONS in virtio-user with vhost-user backend
Date: Wed, 6 Dec 2017 02:55:50 +0000 [thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E3651376137@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20171205144137.GJ9111@yliu-dev>
> -----Original Message-----
> From: Yuanhan Liu [mailto:yliu@fridaylinux.org]
> Sent: Tuesday, December 5, 2017 10:42 PM
> To: Wang, Wei 5. (NSB - CN/Hangzhou)
> Cc: dev@dpdk.org; Tan, Jianfeng
> Subject: Re: [dpdk-dev] The limitation of VHOST_MEMORY_MAX_NREGIONS
> in virtio-user with vhost-user backend
>
> On Tue, Dec 05, 2017 at 06:58:53AM +0000, Wang, Wei 5. (NSB -
> CN/Hangzhou) wrote:
> >
> >
> > Hi, all
> >
> > In DPDK document, it it described that Virtio in containers Cannot work
> when there are more than VHOST_MEMORY_MAX_NREGIONS(8)
> hugepages. In another word, do not use 2MB hugepage so far. Do you know
> the reason of this limitation?
>
> It comes from the vhost-user spec.
>
> > In my envirionment, the pdpe1gb is not set in cpu flag, so hugepage can't
> be set to 1GB size. The hugepage number shall be more than 8
> >
> >
> > So is there any solution or workaround to fix this limitation? Or change
> dpdk code to fix this limitation?
> >
>
> AFAIK, there are no workarounds. And I think the DPDK EAL memory code
> need be
> refactored a bit to fix this limitation. Unforunately, seems there are no work
> on that recently.
For more info, you can refer to: http://dpdk.org/dev/patchwork/patch/10406/
Thanks,
Jianfeng
>
> --yliu
next prev parent reply other threads:[~2017-12-06 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 6:58 Wang, Wei 5. (NSB - CN/Hangzhou)
2017-12-05 14:41 ` Yuanhan Liu
2017-12-06 2:55 ` Tan, Jianfeng [this message]
2017-12-06 2:59 ` Wang, Wei 5. (NSB - CN/Hangzhou)
2017-12-06 11:23 ` Maxime Coquelin
2017-12-06 14:06 ` Yuanhan Liu
2017-12-06 18:22 ` Maxime Coquelin
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=ED26CBA2FAD1BF48A8719AEF02201E3651376137@SHSMSX103.ccr.corp.intel.com \
--to=jianfeng.tan@intel.com \
--cc=dev@dpdk.org \
--cc=wei.5.wang@nokia-sbell.com \
--cc=yliu@fridaylinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).