From: Yuval Avnery <yuvalav@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: Ori Kam <orika@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] regex/mlx5: add dynamic memory registration to datapath
Date: Mon, 5 Oct 2020 11:57:54 +0000 [thread overview]
Message-ID: <CH2PR12MB42464226001EFD7599131D16C80C0@CH2PR12MB4246.namprd12.prod.outlook.com> (raw)
In-Reply-To: <8431823.Zv4F04o16R@thomas>
Fixed in version 3
________________________________
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Sunday, October 4, 2020 10:38 PM
To: Yuval Avnery <yuvalav@nvidia.com>
Cc: Ori Kam <orika@mellanox.com>; dev@dpdk.org <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] regex/mlx5: add dynamic memory registration to datapath
Hi Yuval,
> From: Yuval Avnery <yuvalav@mellanox.com>
>
> Currently job data is being copied to pre-registered buffer.
> To avoid memcpy on the datapath, use dynamic memory registration.
>
> This change will reduce latency when sending regex jobs. The first few
> jobs may have high latency due to registration, but assuming all
> following mbufs will arrive from the same mempool/hugepage, there will
> be no further memory registration.
>
> Signed-off-by: Yuval Avnery <yuvalav@mellanox.com>
> Acked-by: Ori Kam <orika@mellanox.com>
There is a compilation issue:
drivers/regex/mlx5/mlx5_regex.c:200:
undefined reference to `mlx5_os_set_reg_mr_cb'
next prev parent reply other threads:[~2020-10-06 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 11:55 Yuval Avnery
2020-10-04 19:38 ` Thomas Monjalon
2020-10-05 11:57 ` Yuval Avnery [this message]
2020-10-05 10:51 ` [dpdk-dev] [PATCH v3] " Yuval Avnery
2020-10-05 22:59 ` 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=CH2PR12MB42464226001EFD7599131D16C80C0@CH2PR12MB4246.namprd12.prod.outlook.com \
--to=yuvalav@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.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).