DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix minimum number of Multi-Packet RQ buffers
Date: Sun, 5 Aug 2018 11:33:09 +0000	[thread overview]
Message-ID: <DB7PR05MB442656FD6EDE6BB87B649683C3210@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180802210007.10671-1-yskoh@mellanox.com>

Friday, August 3, 2018 12:00 AM, Yongseok Koh:
> Subject: [PATCH] net/mlx5: fix minimum number of Multi-Packet RQ buffers
> 
> If MPRQ is enabled, a PMD-private mempool is allocated. For ConnectX-4 Lx,
> the minimum number of strides is 512 which ConnectX-5 supports 8. This
> results in quite small number of elements for the MPRQ mempool. For
> example, if the size of Rx ring is configured as 512, only one MPRQ buffer can
> cover the whole ring. If there's only one Rx queue is configured. In the
> following code in mlx5_mprq_alloc_mp(), desc is 1 and obj_num will be
> 36 as a result.
> 
> 	desc *= 4;
> 	obj_num = desc + MLX5_MPRQ_MP_CACHE_SZ * priv->rxqs_n;
> 
> However, rte_mempool_create_empty() has a sanity check to refuse large
> per-lcore cache size compared to the number of elements. Cache flush
> threshold should not exceed the number of elements of a mempool. For the
> above example, the threshold is 32 * 1.5 = 48 which is larger than 36 and it
> fails to create the mempool.
> 
> Fixes: 7d6bf6b866b8 ("net/mlx5: add Multi-Packet Rx support")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>

Applied to next-net-mlx, thanks.

      reply	other threads:[~2018-08-05 11:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 21:00 Yongseok Koh
2018-08-05 11:33 ` Shahaf Shuler [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=DB7PR05MB442656FD6EDE6BB87B649683C3210@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=yskoh@mellanox.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).