From: Thomas Monjalon <thomas@monjalon.net>
To: Yuval Avnery <yuvalav@nvidia.com>
Cc: Ori Kam <orika@mellanox.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3] regex/mlx5: add dynamic memory registration to datapath
Date: Tue, 06 Oct 2020 00:59:42 +0200 [thread overview]
Message-ID: <2431948.mpJCyC8Bju@thomas> (raw)
In-Reply-To: <1601895081-19866-1-git-send-email-yuvalav@nvidia.com>
> 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>
Applied, thanks
prev parent reply other threads:[~2020-10-05 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 11:55 [dpdk-dev] [PATCH v2] " Yuval Avnery
2020-10-04 19:38 ` Thomas Monjalon
2020-10-05 11:57 ` Yuval Avnery
2020-10-05 10:51 ` [dpdk-dev] [PATCH v3] " Yuval Avnery
2020-10-05 22:59 ` Thomas Monjalon [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=2431948.mpJCyC8Bju@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=orika@mellanox.com \
--cc=yuvalav@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).