From: "Wang, Xiao W" <xiao.w.wang@intel.com>
To: "Ye, Xiaolong" <xiaolong.ye@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Bie, Tiwei" <tiwei.bie@intel.com>,
"Wang, Zhihong" <zhihong.wang@intel.com>,
Rami Rosen <roszenrami@gmail.com>,
"Wang, Haiyue" <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] examples/vdpa: introduce a new sample for vDPA
Date: Thu, 20 Sep 2018 04:33:49 +0000 [thread overview]
Message-ID: <B7F2E978279D1D49A3034B7786DACF406F9AF210@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20180919222303.GC42303@intel.com>
Hi Xiaolong,
> -----Original Message-----
> From: Ye, Xiaolong
> Sent: Thursday, September 20, 2018 6:23 AM
> To: Wang, Xiao W <xiao.w.wang@intel.com>
> Cc: dev@dpdk.org; Maxime Coquelin <maxime.coquelin@redhat.com>; Bie,
> Tiwei <tiwei.bie@intel.com>; Wang, Zhihong <zhihong.wang@intel.com>;
> Rami Rosen <roszenrami@gmail.com>; Wang, Haiyue
> <haiyue.wang@intel.com>
> Subject: Re: [PATCH v2 2/2] examples/vdpa: introduce a new sample for vDPA
>
> On 09/19, Wang, Xiao W wrote:
> >Hi Xiaolong,
> >
> [snip]
> >> +.. note::
> >> + We need to bind VFIO-pci to VFs before running vdpa sample.
> >
> >Replace "VFIO-pci" with "vfio-pci".
>
> Got it.
>
> >
> >> +
> >> + * modprobe vfio-pci
> >> + * ./usertools/dpdk-devbind.py -b vfio-pci 06:00.2 06:00.3
> >> +
> >> +Then we can create 2 vdpa ports in interactive cmdline.
> >> +
> >> +.. code-block:: console
> >> +
> >> + vdpa> list
> >> + device id device address
> >> + 0 0000:06:00.2
> >> + 1 0000:06:00.3
> >
> >Could we show out also the device's features and supported queue number?
>
> Sure, it's a good suggestion.
>
> [snip]
> >
> >> + ret = rte_vhost_driver_unregister(socket_path);
> >> + if (ret != 0)
> >> + RTE_LOG(ERR, USER1,
> >> + "Fail to unregister vhost driver for %s.\n",
> >> + socket_path);
> >> +}
> >> +
> >> +static void
> >> +vdpa_sample_quit(void)
> >> +{
> >> + int i;
> >> + for (i = 0; i < RTE_MIN(MAX_VDPA_SAMPLE_PORTS, dev_total); i++) {
> >
> >Double " ".
>
> Sorry, not quite understand what's your meaning here.
I mean there are 2 blank spaces after the "<" operator.
BRs,
Xiao
next prev parent reply other threads:[~2018-09-20 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 18:06 [dpdk-dev] [PATCH v2 1/2] vhost: introduce API to get vDPA device number Xiaolong Ye
2018-09-13 18:06 ` [dpdk-dev] [PATCH v2 2/2] examples/vdpa: introduce a new sample for vDPA Xiaolong Ye
2018-09-19 14:46 ` Wang, Xiao W
2018-09-19 22:23 ` Ye Xiaolong
2018-09-20 4:33 ` Wang, Xiao W [this message]
2018-09-19 14:46 ` [dpdk-dev] [PATCH v2 1/2] vhost: introduce API to get vDPA device number Wang, Xiao W
2018-09-19 22:17 ` Ye Xiaolong
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=B7F2E978279D1D49A3034B7786DACF406F9AF210@SHSMSX101.ccr.corp.intel.com \
--to=xiao.w.wang@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=roszenrami@gmail.com \
--cc=tiwei.bie@intel.com \
--cc=xiaolong.ye@intel.com \
--cc=zhihong.wang@intel.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).