DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/8] QoS features on i40e - Linux kernel divergence
Date: Tue, 28 Feb 2017 05:04:35 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B5694B6@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <eddb259e-1091-5ce6-bee9-9046d754bec9@6wind.com>

Hi Vincent,

> -----Original Message-----
> From: Vincent JARDIN [mailto:vincent.jardin@6wind.com]
> Sent: Friday, February 24, 2017 5:14 PM
> To: Lu, Wenzhuo; Stephen Hemminger
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/8] QoS features on i40e - Linux kernel
> divergence
> 
> Le 24/02/2017 à 08:23, Lu, Wenzhuo a écrit :
> >> It is good to allow setting QoS on device, but it looks like this is
> >> a device specific API, not a generic PMD function. I don't think any
> >> feature in DPDK should be hardcoded to one device type.
> > Yes, they're private APIs.
> > Normally we want to support kernel PF + dpdk VF. As there's no PF - VF
> interface defined for QoS, These features cannot be implemented on VF now.
> > Have to put them on PF, and let PF play as a controller.
> > There's discussion about if we should rich PF host features. So, I put these
> functions to rte_pmd_i40e.h to show they're experimental and temporary
> features.
> >
> > There's another thread started by Cristian for a generic QoS solution. After it's
> accepted and the PF-VF interfaces are defined by kernel driver. We can use a
> generic solution to replace this one.
> 
> Same, DPDK continues to diverge from the Linux kernel for PF capabilities. Intel
> did commit previously that you'll do some works for proper PF support into the
> kernel to avoid it. It is not happening. So, I would rather keep nack'ing such
> series unless:
>    - either it is under experimental compilation option
Yes, they're experimental. I put the functions in the rte_pmd_i40e.h. All the functions in this file are announced experimental.

>    - either it is showing up into the kernel
We're discussing this internally in parallel.

> 
> Best regards,
>    Vincent

  reply	other threads:[~2017-02-28  5:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  3:24 [dpdk-dev] [PATCH 0/8] QoS features on i40e Wenzhuo Lu
2017-02-24  3:24 ` [dpdk-dev] [PATCH 1/8] net/i40e: set VF max bandwidth from PF Wenzhuo Lu
2017-03-24  5:01   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 2/8] net/i40e: allocate VF TC " Wenzhuo Lu
2017-03-24  5:10   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 3/8] net/i40e: set VF TC max " Wenzhuo Lu
2017-03-24  5:15   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 4/8] net/i40e: set TC strict priority mode Wenzhuo Lu
2017-03-24  5:19   ` Wu, Jingjing
2017-03-24  7:07     ` Lu, Wenzhuo
2017-03-24  9:34       ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 5/8] app/testpmd: set VF TX max bandwidth Wenzhuo Lu
2017-03-24  5:21   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 6/8] app/testpmd: set VF TC TX min bandwidth Wenzhuo Lu
2017-03-24  5:22   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 7/8] app/testpmd: set VF TC TX max bandwidth Wenzhuo Lu
2017-03-24  5:22   ` Wu, Jingjing
2017-02-24  3:24 ` [dpdk-dev] [PATCH 8/8] app/testpmd: set TC strict link priority mode Wenzhuo Lu
2017-03-24  5:23   ` Wu, Jingjing
2017-02-24  6:55 ` [dpdk-dev] [PATCH 0/8] QoS features on i40e Stephen Hemminger
2017-02-24  7:23   ` Lu, Wenzhuo
2017-02-24  9:14     ` [dpdk-dev] [PATCH 0/8] QoS features on i40e - Linux kernel divergence Vincent JARDIN
2017-02-28  5:04       ` Lu, Wenzhuo [this message]
2017-03-27 15:13 ` [dpdk-dev] [PATCH 0/8] QoS features on i40e 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=6A0DE07E22DDAD4C9103DF62FEBC09093B5694B6@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=vincent.jardin@6wind.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).