DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] ixgbe: vector pmd fixes
Date: Thu, 23 Oct 2014 01:40:34 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F96251187C4B7@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1413975345-24326-1-git-send-email-bruce.richardson@intel.com>

Hi,

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Wednesday, October 22, 2014 6:56 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/2] ixgbe: vector pmd fixes
> 
> This patch set contains small fixes for issues with the vector PMD.
> The issues and the fixes for them are described in each patch individually.
> 
> Bruce Richardson (2):
>   ixgbe: remove static qualifier for thread safety
>   ixgbe: always perform vec RX setup if vpmd enabled
> 
>  lib/librte_pmd_ixgbe/ixgbe_rxtx.c     | 4 +++-
>  lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c | 2 +-
>  2 files changed, 4 insertions(+), 2 deletions(-)
> 
> --
> 1.9.3

Acked-by: Changchun Ouyang <Changchun.ouyang@intel.com>

  parent reply	other threads:[~2014-10-23  1:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 10:55 Bruce Richardson
2014-10-22 10:55 ` [dpdk-dev] [PATCH 1/2] ixgbe: remove static qualifier for thread safety Bruce Richardson
2014-10-22 23:43   ` Masaru Oki
2014-10-24 10:34     ` Bruce Richardson
2014-10-24 11:00       ` Masaru Oki
2014-10-22 10:55 ` [dpdk-dev] [PATCH 2/2] ixgbe: always perform vec RX setup if vpmd enabled Bruce Richardson
2014-10-23  1:40 ` Ouyang, Changchun [this message]
2014-10-29 23:33   ` [dpdk-dev] [PATCH 0/2] ixgbe: vector pmd fixes Thomas Monjalon

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=F52918179C57134FAEC9EA62FA2F96251187C4B7@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=bruce.richardson@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).