DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	wang wei <lnykww@gmail.com>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] net/ixgbe: start rxtx after all nic config done.
Date: Wed, 21 Sep 2016 00:46:47 +0000	[thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC090939329464@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <a5384d1e-92df-40a1-ec1e-210f1726d80f@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, September 20, 2016 10:18 PM
> To: Lu, Wenzhuo; wang wei; thomas.monjalon@6wind.com
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] net/ixgbe: start rxtx after all nic config done.
> 
> Hi Wenzhuo,
> 
> On 9/8/2016 2:07 AM, Lu, Wenzhuo wrote:
> > Hi Wei,
> >
> >
> >> -----Original Message-----
> >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of wang wei
> >> Sent: Tuesday, September 6, 2016 8:05 PM
> >> To: thomas.monjalon@6wind.com
> >> Cc: dev@dpdk.org
> >> Subject: [dpdk-dev] [RFC] net/ixgbe: start rxtx after all nic config done.
> >>
> >> if start rxtx before flow director config, will cause driver can't
> >> receive packets from nic.
> >>
> >> Signed-off-by: wang wei <lnykww@gmail.com>
> > I think you're right. We should start rx/tx after the config is done.
> >
> 
> Is this an Ack?
Yes. 

  reply	other threads:[~2016-09-21  0:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 12:05 wang wei
2016-09-07  1:33 ` Wu, Jingjing
2016-09-07  4:30   ` wei wang
2016-09-08  1:07 ` Lu, Wenzhuo
2016-09-20 14:17   ` Ferruh Yigit
2016-09-21  0:46     ` Lu, Wenzhuo [this message]
2016-09-21  9:28       ` Ferruh Yigit
2016-09-21 12:36         ` Bruce Richardson

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=6A0DE07E22DDAD4C9103DF62FEBC090939329464@shsmsx102.ccr.corp.intel.com \
    --to=wenzhuo.lu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lnykww@gmail.com \
    --cc=thomas.monjalon@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).