DPDK patches and discussions
 help / color / mirror / Atom feed
From: Declan Doherty <declan.doherty@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, Zhe Tao <zhe.tao@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] examples/dpdk_qat: Fix RX queue start number to the one just received the packets
Date: Mon, 7 Dec 2015 08:47:10 +0000	[thread overview]
Message-ID: <5665478E.1000200@intel.com> (raw)
In-Reply-To: <1932701.vd3GWY9UVx@xps13>

On 07/12/15 01:32, Thomas Monjalon wrote:
> 2015-09-29 19:07, Zhe Tao:
>> Every time we started to receive the packets, the start queue number
>> should be the one that just received the packets, should not start from zero!
>>
> [...]
>> -		for (i = 0; i < qconf->n_rx_queue; i++) {
>> +		for (i = qconf->rx_curr_queue; i < qconf->n_rx_queue; i++) {
>
> Anyone to confirm?
>

I'll have a look at this this morning Thomas.

  reply	other threads:[~2015-12-07  8:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 11:07 Zhe Tao
2015-12-07  1:32 ` Thomas Monjalon
2015-12-07  8:47   ` Declan Doherty [this message]
2016-03-04  8:19 ` Wu, Jingjing

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=5665478E.1000200@intel.com \
    --to=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=zhe.tao@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).