From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>,
"Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V1 1/2][vhost peer conf] conf: add cfg file of vhost peer direct connection
Date: Wed, 7 Aug 2019 03:46:04 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAFED0B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1563313688-4457-1-git-send-email-lihongx.ma@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Wednesday, July 17, 2019 5:48 AM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>; Ma, LihongX
> <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1 1/2][vhost peer conf] conf: add cfg file of vhost peer
> direct connection
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> conf/vhost_peer_conf.cfg | 10 ++++++++++
> 1 file changed, 10 insertions(+)
> create mode 100644 conf/vhost_peer_conf.cfg
>
> diff --git a/conf/vhost_peer_conf.cfg b/conf/vhost_peer_conf.cfg new file
> mode 100644 index 0000000..63346e9
> --- /dev/null
> +++ b/conf/vhost_peer_conf.cfg
> @@ -0,0 +1,10 @@
> +# Connect two fortville 40G nic port directly on DUT [peerconf] # pci
> +of Port0 pci= # driver of Port0 and Port1 pci_drv= # pci of Port1 peer=
> +# intf of Port1 peer_intf=
> --
> 2.7.4
prev parent reply other threads:[~2019-08-07 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 21:48 lihong
2019-07-16 21:48 ` [dts] [PATCH V1 2/2][vhost peer conf] tests: add common method file to read conf file lihong
2019-07-17 6:18 ` Wang, Yinan
2019-07-17 6:21 ` Ma, LihongX
2019-08-07 3:46 ` Tu, Lijuan
2019-07-17 6:18 ` [dts] [PATCH V1 1/2][vhost peer conf] conf: add cfg file of vhost peer direct connection Wang, Yinan
2019-07-17 6:22 ` Ma, LihongX
2019-08-07 3:46 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BAFED0B@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--cc=yinan.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).