DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, lijuan.tu@intel.com, juraj.linkes@pantheon.tech,
	ohilyard@iol.unh.edu, david.marchand@redhat.com,
	thomas@monjalon.net, david.hunt@intel.com, ruifeng.wang@arm.com,
	nd@arm.com, reshma.pattan@intel.com, stable@dpdk.org
Subject: Re: [PATCH] examples/distributor: one Tx queue is enough
Date: Tue, 8 Mar 2022 10:00:43 +0000	[thread overview]
Message-ID: <YicpS/e3vjNN+2kl@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220307223946.578201-1-honnappa.nagarahalli@arm.com>

On Mon, Mar 07, 2022 at 10:39:46PM +0000, Honnappa Nagarahalli wrote:
> Distributor application creates one Tx queue per core. However
> the transmit is done only from a single core. Hence creating
> one Tx queue is enough.
> 
> Fixes: 07db4a975094 ("examples/distributor: new sample app")
> Cc: bruce.richardson@intel.com
> Cc: reshma.pattan@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> ---
> DTS test cases make this change to DPDK. However, I find that, one
> queue is enough. Hence we could make this change in DPDK.
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Do we know why DTS is making this change? Does having more TX queues than
necessary cause problems?

  parent reply	other threads:[~2022-03-08 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 22:39 Honnappa Nagarahalli
2022-03-08  3:26 ` Honnappa Nagarahalli
2022-03-08 10:00 ` Bruce Richardson [this message]
2022-03-08 11:40   ` Thomas Monjalon
2022-03-08 14:55   ` Tu, Lijuan

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=YicpS/e3vjNN+2kl@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.hunt@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=nd@arm.com \
    --cc=ohilyard@iol.unh.edu \
    --cc=reshma.pattan@intel.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).