patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Han, YingyaX" <yingyax.han@intel.com>,
	"Li, Xiaoyun" <xiaoyun.li@intel.com>,
	"Jiang, JunyuX" <junyux.jiang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3] examples/vmdq: fix the output of pools/queues
Date: Tue, 31 Mar 2020 15:35:55 +0100	[thread overview]
Message-ID: <d6db7db4-7d6c-da40-83c3-6a5dae239978@intel.com> (raw)
In-Reply-To: <BN7PR11MB2818EE1C1A26B84BBF1FC5E0FFCB0@BN7PR11MB2818.namprd11.prod.outlook.com>

On 3/30/2020 3:21 AM, Han, YingyaX wrote:
> Tested-by: Han,YingyaX <yingyax.han@intel.com>
> 
> BRs,
> Yingya
> -----Original Message-----
> From: stable <stable-bounces@dpdk.org> On Behalf Of Li, Xiaoyun
> Sent: Monday, March 2, 2020 3:19 PM
> To: Jiang, JunyuX <junyux.jiang@intel.com>; dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; stable@dpdk.org
> Subject: Re: [dpdk-stable] [PATCH v3] examples/vmdq: fix the output of pools/queues
> 
> Hi
>> -----Original Message-----
>> From: Jiang, JunyuX
>> Sent: Monday, March 2, 2020 14:41
>> To: dev@dpdk.org
>> Cc: Li, Xiaoyun <xiaoyun.li@intel.com>; Yang, Qiming 
>> <qiming.yang@intel.com>; Jiang, JunyuX <junyux.jiang@intel.com>; 
>> stable@dpdk.org
>> Subject: [PATCH v3] examples/vmdq: fix the output of pools/queues
>>
>> To match the pools/queues configuration, the pools/queues output 
>> should start from VMDQ base queue. This patch fixed the issue.
>>
>> Fixes: 6bb97df521aa ("examples/vmdq: new app")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Junyu Jiang <junyux.jiang@intel.com>
>> ---
>>  examples/vmdq/main.c | 9 +++++----
>>  1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/examples/vmdq/main.c b/examples/vmdq/main.c index
>> 011110920..5ab3427c0 100644
>> --- a/examples/vmdq/main.c
>> +++ b/examples/vmdq/main.c
>> @@ -441,10 +441,11 @@ update_mac_address(struct rte_mbuf *m, unsigned
>> dst_port)  static void  sighup_handler(int signum)  {
>> -	unsigned q;
>> -	for (q = 0; q < num_queues; q++) {
>> -		if (q % (num_queues/num_pools) == 0)
>> -			printf("\nPool %u: ", q/(num_queues/num_pools));
>> +	unsigned int q = vmdq_queue_base;
>> +	for (; q < num_queues; q++) {
>> +		if ((q - vmdq_queue_base) % (num_vmdq_queues / num_pools)
>> == 0)
>> +			printf("\nPool %u: ", (q - vmdq_queue_base) /
>> +			       (num_vmdq_queues / num_pools));
>>  		printf("%lu ", rxPackets[q]);
>>  	}
>>  	printf("\nFinished handling signal %d\n", signum);
>> --
>> 2.17.1
> 
> Acked-by: Xiaoyun Li <Xiaoyun.li@intel.com>
> 

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2020-03-31 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  7:57 [dpdk-stable] [PATCH] " Junyu Jiang
2020-02-26  8:35 ` [dpdk-stable] [PATCH v2] " Junyu Jiang
2020-03-02  2:35   ` [dpdk-stable] [dpdk-dev] " Yang, Qiming
2020-03-02  3:10   ` [dpdk-stable] " Li, Xiaoyun
2020-03-02  6:41   ` [dpdk-stable] [PATCH v3] " Junyu Jiang
2020-03-02  7:19     ` Li, Xiaoyun
2020-03-30  2:21       ` Han, YingyaX
2020-03-31 14:35         ` Ferruh Yigit [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=d6db7db4-7d6c-da40-83c3-6a5dae239978@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=junyux.jiang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiaoyun.li@intel.com \
    --cc=yingyax.han@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).