From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Stojaczyk, DariuszX" <dariuszx.stojaczyk@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Yuanhan Liu <yliu@fridaylinux.org>
Cc: "Harris, James R" <james.r.harris@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] virtio with 2MB hugepages - bringing back single file segments
Date: Fri, 2 Mar 2018 11:00:04 +0100 [thread overview]
Message-ID: <f3962667-63fd-fcdd-d516-ff3b37e2876f@redhat.com> (raw)
In-Reply-To: <FBE7E039FA50BF47A673AD0BD3CD56A837597A05@HASMSX105.ger.corp.intel.com>
On 03/02/2018 10:03 AM, Stojaczyk, DariuszX wrote:
> Hi Maxime,
>
>>> Hi,
>>>
>>> I'm trying to make a vhost-user initiator built upon DPDK work with
>>> 2MB hugepages. In the initiator we have to share all memory with the host
>> process, so it can perform DMA. DPDK currently enforces having one descriptor
>> per hugepage and there's an artificial limit of shared descriptors in DPDK
>> vhost-user implementation (currently 8). Because of that, all DPDK vhost-user
>> initiators are practically limited to 1GB hugepages at the moment. We can
>> always increase the artificial descriptor limit, but then we're limited by
>> sendmsg() itself, which on Linux accepts no more than 253 descriptors.
>> However, could we increase the vhost-user implementation limit to - say - 128,
>> and bring back "single file segments" [1]?
>>
>> If you do something like this, you'll have first to update the vhost-user spec,
>> which should I think include a new protocol feature bit.
>
> Do I? I can't see any memory region limitation in the vhost-user spec [1]. If a 128-region initiator tries to connect to an 8-region rte_vhost, the recvmsg() would simply fail - rte_vhost rejects `truncated` messages.
Here it is:
* Memory regions description
---------------------------------------------------
| num regions | padding | region0 | ... | region7 |
---------------------------------------------------
Num regions: a 32-bit number of regions
Padding: 32-bit
>
>>
>> Also, you will have to consider improving the translation functions with a better
>> search algorithm, else you'll have very poor performance.
>
> That's right, I got that sorted out already.
>
> Regards,
> D.
>
> [1] https://github.com/qemu/qemu/blob/master/docs/interop/vhost-user.txt
>
prev parent reply other threads:[~2018-03-02 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 22:40 Stojaczyk, DariuszX
2018-03-02 2:36 ` Tan, Jianfeng
2018-03-02 7:33 ` Maxime Coquelin
2018-03-02 9:03 ` Stojaczyk, DariuszX
2018-03-02 10:00 ` Maxime Coquelin [this message]
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=f3962667-63fd-fcdd-d516-ff3b37e2876f@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dariuszx.stojaczyk@intel.com \
--cc=dev@dpdk.org \
--cc=james.r.harris@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=thomas@monjalon.net \
--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).