From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] remove unused code of DPDK version
Date: Tue, 29 Aug 2017 01:33:25 +0000 [thread overview]
Message-ID: <94479800C636CB44BD422CB454846E0132015250@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <b7a0910a-9a49-b6ce-b77e-69e16b42a164@intel.com>
Hi Ferruh,
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, August 28, 2017 7:22 PM
> To: Xing, Beilei <beilei.xing@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/3] remove unused code of DPDK version
>
> On 8/23/2017 9:44 AM, Beilei Xing wrote:
> > Since there's no specific version number to distinguish DPDK pf and
> > Linux kernel pf, DPDK vf won't recognize if host is DPDK pf or kernel
> > pf. The specific virtual channel commands for DPDK pf and code of DPDK
> > version can be deleted.
>
> Is DPDK i40e PF becomes functionally same with Linux i40e PF after this
> patchset?
Yes, they use the same virtual channels.
>
> >
> > Beilei Xing (3):
> > net/i40e: remove virtual channel command for VLAN pvid
> > net/i40e: remove virtual channel command for VSI queue
> > net/i40e: remove DPDK PF version specific code
> >
> <...>
next prev parent reply other threads:[~2017-08-29 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 8:44 Beilei Xing
2017-08-23 8:44 ` [dpdk-dev] [PATCH 1/3] net/i40e: remove virtual channel command for VLAN pvid Beilei Xing
2017-08-23 8:44 ` [dpdk-dev] [PATCH 2/3] net/i40e: remove virtual channel command for VSI queue Beilei Xing
2017-08-23 8:44 ` [dpdk-dev] [PATCH 3/3] net/i40e: remove DPDK PF version specific code Beilei Xing
2017-08-28 11:21 ` [dpdk-dev] [PATCH 0/3] remove unused code of DPDK version Ferruh Yigit
2017-08-29 1:33 ` Xing, Beilei [this message]
2017-08-30 8:31 ` Ferruh Yigit
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=94479800C636CB44BD422CB454846E0132015250@SHSMSX101.ccr.corp.intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@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).