All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Narayana Prasad Raju Athreya <pathreya@marvell.com>,
	Shally Verma <shallyv@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/octeontx: use distinct metabuf pool for each queue
Date: Wed, 8 May 2019 12:16:34 +0100	[thread overview]
Message-ID: <b384c94f-b3c1-996a-6636-988bc3cae6a7@redhat.com> (raw)
In-Reply-To: <20190418032953.2102-1-anoobj@marvell.com>

On 18/04/2019 04:30, Anoob Joseph wrote:
> The metabuf pool is shared across all queue pairs belonging to the
> PMD. In order to prevent one queue pair from starving another,
> use a distinct mempool for each queue pair.
> 
> Fixes: 273487f7b381 ("crypto/octeontx: add global resource init")
> 

Hi Anoob,

This won't apply on stable, the code has changed quite a bit on master.
Please send a backport for 18.11 stable branch, or let me know if it's
not needed.

thanks,
Kevin.

> Signed-off-by: Anoob Joseph <anoobj@marvell.com>


  parent reply	other threads:[~2019-05-08 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  3:30 [dpdk-dev] [PATCH] crypto/octeontx: use distinct metabuf pool for each queue Anoob Joseph
2019-04-18  5:20 ` [dpdk-dev] [PATCH v2] " Anoob Joseph
2019-04-30  7:02   ` [dpdk-dev] [EXT] " Akhil Goyal
2019-04-30  8:40     ` Anoob Joseph
2019-04-30 13:50       ` Akhil Goyal
2019-05-01  2:49         ` Anoob Joseph
2019-05-01 14:08           ` Akhil Goyal
2019-04-30  7:19   ` [dpdk-dev] " Shally Verma
2019-05-08 11:16 ` Kevin Traynor [this message]
2019-05-08 15:11   ` [dpdk-dev] [EXT] Re: [PATCH] " Anoob Joseph

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=b384c94f-b3c1-996a-6636-988bc3cae6a7@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=pathreya@marvell.com \
    --cc=shallyv@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.