From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Suanming Mou <suanmingm@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH v2] net/mlx5: replenish MPRQ buffers for miniCQEs
Date: Mon, 22 Jul 2024 12:16:41 +0000 [thread overview]
Message-ID: <PH0PR12MB880011FCC2570E4636ABC5ABA4A82@PH0PR12MB8800.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231101145710.2356260-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, November 1, 2023 15:57
> To: dev@dpdk.org
> Cc: Suanming Mou <suanmingm@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2] net/mlx5: replenish MPRQ buffers for miniCQEs
>
> Keep unzipping if the next CQE is the miniCQE array in
> rxq_cq_decompress_v() routine only for non-MPRQ scenario, MPRQ requires
> buffer replenishment between the miniCQEs.
>
> Restore the check for the initial compressed CQE for SPRQ and check that the
> current CQE is not compressed before copying it as a possible title CQE.
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2024-07-22 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:43 [PATCH] " Alexander Kozyrev
2023-11-01 14:57 ` [PATCH v2] " Alexander Kozyrev
2024-07-22 12:16 ` Dariusz Sosnowski [this message]
2024-07-22 15:03 ` Raslan Darawsheh
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=PH0PR12MB880011FCC2570E4636ABC5ABA4A82@PH0PR12MB8800.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=rasland@nvidia.com \
--cc=suanmingm@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).