DPDK patches and discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@nvidia.com>
To: viacheslavo@nvidia.com, matan@nvidia.com
Cc: rasland@nvidia.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] net/mlx5: hash list optimization
Date: Wed,  2 Dec 2020 19:39:23 +0800	[thread overview]
Message-ID: <1606909165-164407-1-git-send-email-suanmingm@nvidia.com> (raw)

This patch set contains the hash list optimization for the lock and memory.

Suanming Mou (2):
  net/mlx5: optimize hash list synchronization
  net/mlx5: optimize the hash list entry memory

 drivers/net/mlx5/linux/mlx5_os.c |  5 ++-
 drivers/net/mlx5/mlx5.c          |  3 +-
 drivers/net/mlx5/mlx5_flow.c     | 43 ++++++++++++++++----
 drivers/net/mlx5/mlx5_flow.h     | 23 +++++++++--
 drivers/net/mlx5/mlx5_flow_dv.c  | 57 +++++++++++++++++++--------
 drivers/net/mlx5/mlx5_utils.c    | 85 ++++++++++++++++++++--------------------
 drivers/net/mlx5/mlx5_utils.h    | 16 +++++---
 7 files changed, 155 insertions(+), 77 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2020-12-02 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 11:39 Suanming Mou [this message]
2020-12-02 11:39 ` [dpdk-dev] [PATCH 1/2] net/mlx5: optimize hash list synchronization Suanming Mou
2020-12-02 11:39 ` [dpdk-dev] [PATCH 2/2] net/mlx5: optimize the hash list entry memory Suanming Mou
2020-12-03  2:18 ` [dpdk-dev] [PATCH v2 0/2] net/mlx5: hash list optimization Suanming Mou
2020-12-03  2:18   ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: optimize hash list synchronization Suanming Mou
2020-12-03  2:18   ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: optimize the hash list entry memory Suanming Mou
2020-12-08 23:40   ` [dpdk-dev] [PATCH v2 0/2] net/mlx5: hash list optimization 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=1606909165-164407-1-git-send-email-suanmingm@nvidia.com \
    --to=suanmingm@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@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).