From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Dmitry Kozlyuk <dkozlyuk@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] common/mlx5: fix MR lookup on slow path
Date: Fri, 26 Nov 2021 08:52:47 +0000 [thread overview]
Message-ID: <DM6PR12MB37530FB8BBA011D21F005825DF639@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211125202044.3483813-1-dkozlyuk@nvidia.com>
> -----Original Message-----
> From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> Sent: Thursday, November 25, 2021 22:21
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> Raslan Darawsheh <rasland@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] common/mlx5: fix MR lookup on slow path
>
> Memory region (MR) was being looked up incorrectly for the data address of
> an externally-attached mbuf.
> A search was attempted for the mempool of the mbuf, while mbuf data
> address does not belong to this mempool in case of externally-attached mbuf.
> Only attempt the search:
> 1) for not externally-attached mbufs;
> 2) for mbufs coming from MPRQ mempool;
> 3) for externally-attached mbufs from mempools
> with pinned external buffers.
>
> Fixes: 08ac03580ef2 ("common/mlx5: fix mempool registration")
>
> Signed-off-by: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
> Reviewed-by: Matan Azrad <matan@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2021-11-26 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 20:20 Dmitry Kozlyuk
2021-11-26 8:52 ` Slava Ovsiienko [this message]
2021-11-26 12:28 ` Thomas Monjalon
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=DM6PR12MB37530FB8BBA011D21F005825DF639@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--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).