DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] add i40e RSS support in VF
Date: Wed, 20 Aug 2014 07:07:07 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A77FC07@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1405651521-14545-1-git-send-email-helin.zhang@intel.com>



> -----Original Message-----
> From: Zhang, Helin
> Sent: Friday, July 18, 2014 10:45 AM
> To: dev@dpdk.org
> Cc: Zhang, Helin
> Subject: [PATCH 0/3] add i40e RSS support in VF
> 
> As RSS in i40e VF is supported by hardware, these patches enable it in i40e
> PMD, and also enable its testing in testpmd.
> 
> Helin Zhang (3):
>   i40evf: add RSS support in VF
>   app/testpmd: enable RSS support for i40e
>   ethdev: improvements for some macro definition in head file
> 
>  app/test-pmd/testpmd.c               |  13 ++-
>  lib/librte_ether/rte_ethdev.h        |  47 ++++----
>  lib/librte_pmd_i40e/i40e_ethdev.c    |   4 +-
>  lib/librte_pmd_i40e/i40e_ethdev.h    |  40 ++++++-
>  lib/librte_pmd_i40e/i40e_ethdev_vf.c | 208
> +++++++++++++++++++++++++++++++++++
>  5 files changed, 284 insertions(+), 28 deletions(-)
> 
> --
> 1.8.1.4


Hi guys

Any comments for these patches?
Any next steps planned for merging these patches?

Regards,
Helin

      parent reply	other threads:[~2014-08-20  7:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  2:45 Helin Zhang
2014-07-18  2:45 ` [dpdk-dev] [PATCH 1/3] i40evf: add " Helin Zhang
2014-07-18  2:45 ` [dpdk-dev] [PATCH 2/3] app/testpmd: enable RSS support for i40e Helin Zhang
2014-08-27 15:36   ` Thomas Monjalon
2014-07-18  2:45 ` [dpdk-dev] [PATCH 3/3] ethdev: improvements for some macro definition in head file Helin Zhang
2014-08-27 15:42   ` Thomas Monjalon
2014-07-31  1:55 ` [dpdk-dev] [PATCH 0/3] add i40e RSS support in VF Zhan, Zhaochen
2014-08-20  7:07 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A77FC07@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    /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).