DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6] net/fm10k: add support for check descriptor status APIs
Date: Mon, 2 Jul 2018 01:46:43 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07E02E56@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <6b08385f-48e2-ad69-46b1-3495aefc5a99@intel.com>

Hi, Ferruh

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, June 29, 2018 7:04 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v6] net/fm10k: add support for check
> descriptor status APIs
> 
> On 6/29/2018 2:48 AM, Wei Zhao wrote:
> > rte_eth_rx_descritpr_status and rte_eth_tx_descriptor_status are
> > supported by fm10K.
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> >
> > ---
> >
> > v2:
> > -fix DD check error in tx descriptor
> >
> > v3:
> > -fix DD check index error
> >
> > v4:
> > -fix error in RS bit list poll
> >
> > v5:
> > -rebase code to branch and delete useless variable
> >
> > v6:
> > -change release note
> > ---
> >  doc/guides/rel_notes/release_18_08.rst |  6 +++
> >  drivers/net/fm10k/fm10k.h              |  7 +++
> >  drivers/net/fm10k/fm10k_ethdev.c       |  2 +
> >  drivers/net/fm10k/fm10k_rxtx.c         | 78
> ++++++++++++++++++++++++++++++++++
> 
> Can you please update fm10k*.ini files to announce newly added "Rx
> descriptor status" & "Tx descriptor status" features?

Ok, thank you. I will commit new patch.

  reply	other threads:[~2018-07-02  1:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08  8:36 [dpdk-dev] [PATCH 0/2] " Wei Zhao
2018-02-08  8:36 ` [dpdk-dev] [PATCH 1/2] net/e1000: " Wei Zhao
2018-06-20  8:52   ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-06-27  8:37     ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-29  1:52       ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-07-02  7:42         ` Zhao1, Wei
2018-07-02 13:03           ` Zhang, Qi Z
2018-07-02 13:12             ` Zhang, Qi Z
2018-02-08  8:36 ` [dpdk-dev] [PATCH 2/2] net/fm10k: " Wei Zhao
2018-06-20  8:44   ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-06-22  7:53     ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-22  8:20       ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-06-27  8:10         ` Zhang, Qi Z
2018-06-27  8:18           ` Zhao1, Wei
2018-06-27  8:18         ` Zhang, Qi Z
2018-06-27  9:09           ` Zhao1, Wei
2018-06-27  8:24         ` [dpdk-dev] [PATCH v5] " Wei Zhao
2018-06-27  8:26         ` Wei Zhao
2018-06-29  1:48           ` [dpdk-dev] [PATCH v6] " Wei Zhao
2018-06-29 11:03             ` Ferruh Yigit
2018-07-02  1:46               ` Zhao1, Wei [this message]
2018-07-02  7:15             ` [dpdk-dev] [PATCH v7] " Zhao Wei
2018-07-02 13:07               ` Zhang, Qi Z
2018-07-02 13:11                 ` Zhang, Qi Z
2018-06-27 12:49         ` [dpdk-dev] [PATCH v4] " Zhang, Qi Z
2018-06-29  1:22           ` Zhao1, Wei

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=A2573D2ACFCADC41BB3BE09C6DE313CA07E02E56@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=qi.z.zhang@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).