From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH v3] net/mlx5: handle MPRQ incompatibility with external buffers
Date: Tue, 12 Apr 2022 08:08:01 +0000 [thread overview]
Message-ID: <BYAPR12MB30787530FDA8FDFCD3242858CFED9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220311230825.3904165-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Saturday, March 12, 2022 1:08 AM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH v3] net/mlx5: handle MPRQ incompatibility with external
> buffers
>
> Multi-Packet Rx queue uses PMD-managed buffers to store packets.
> These buffers are externally attached to user mbufs.
> This conflicts with the feature that allows using user-managed externally
> attached buffers in an application.
> Fall back to SPRQ in case external buffers mempool is configured.
> Add the corresponding limitation to MLX5 documentation that MPRQ and
> external data buffers cannot be used together.
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> ---
> v3: fixed coverity issue with NULL pointer derefence
> v2: fixed typo in warning message
>
Patch rebased and applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-04-12 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 23:40 [PATCH] " Alexander Kozyrev
2022-03-10 23:45 ` [PATCH v2] " Alexander Kozyrev
2022-03-11 23:08 ` [PATCH v3] " Alexander Kozyrev
2022-03-14 8:50 ` Slava Ovsiienko
2022-04-12 8:08 ` Raslan Darawsheh [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=BYAPR12MB30787530FDA8FDFCD3242858CFED9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=viacheslavo@nvidia.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).