DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chen, Jing D" <jing.d.chen@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Qiu, Michael" <michael.qiu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] fm10k: Fix queue start twice failed
Date: Tue, 31 Mar 2015 06:37:44 +0000	[thread overview]
Message-ID: <4341B239C0EFF9468EE453F9E9F4604D016B2E1D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2187092.gF6NabJ8tm@xps13>

Hi, Thomas,


> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Tuesday, March 31, 2015 4:02 AM
> To: Qiu, Michael
> Cc: dev@dpdk.org; Chen, Jing D
> Subject: Re: [dpdk-dev] [PATCH] fm10k: Fix queue start twice failed
> 
> 2015-03-25 18:48, Michael Qiu:
> > When use "port 0 rxq 0 start" in testpmd twice, the rx queue 0 on
> > port 0 will failed to work.
> >
> > The root casue is the rxqctl enable bit need to reset if already
> > enabled.
> 
> Please try to reword this message to make it clear.
> 
> > Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> > ---
> >  lib/librte_pmd_fm10k/fm10k_ethdev.c | 56 +++++++++++++++++++++---
> -------------
> >  1 file changed, 32 insertions(+), 24 deletions(-)
> 
> Jing, should it enter in 2.0?

Michael and I discussed and thought it's not the best solution to fix this issue. So, we'd like postpone this fix.

Thanks!


> 

      reply	other threads:[~2015-03-31  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 10:48 Michael Qiu
2015-03-30 20:02 ` Thomas Monjalon
2015-03-31  6:37   ` Chen, Jing D [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=4341B239C0EFF9468EE453F9E9F4604D016B2E1D@shsmsx102.ccr.corp.intel.com \
    --to=jing.d.chen@intel.com \
    --cc=dev@dpdk.org \
    --cc=michael.qiu@intel.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).