From: "Zhu, Heqing" <heqing.zhu@intel.com>
To: "Zhangkun (K)" <zhang.zhangkun@huawei.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] multiqueue is supported by vhost user?
Date: Thu, 25 Sep 2014 14:51:42 +0000 [thread overview]
Message-ID: <CAD16F236028A64DBBC0158B1636EA4510F62062@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <0FCB215400789046A95ECE23C3E46C515F962F8A@szxema505-mbx.china.huawei.com>
It is not supported yet. Do you want to send patches to add this support?
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhangkun (K)
Sent: Thursday, September 25, 2014 11:28 AM
To: dev@dpdk.org
Subject: [dpdk-dev] multiqueue is supported by vhost user?
Hi,
Multiqueue is supported by vhost user?
If not supported now , will it be supported in the future?
next prev parent reply other threads:[~2014-09-25 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 3:27 Zhangkun (K)
2014-09-25 14:51 ` Zhu, Heqing [this message]
2014-09-26 1:42 ` Zhangkun (K)
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=CAD16F236028A64DBBC0158B1636EA4510F62062@SHSMSX104.ccr.corp.intel.com \
--to=heqing.zhu@intel.com \
--cc=dev@dpdk.org \
--cc=zhang.zhangkun@huawei.com \
/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).