DPDK patches and discussions
 help / color / mirror / Atom feed
From: Slava Ovsiienko <viacheslavo@mellanox.com>
To: Bing Zhao <bingz@mellanox.com>, Ori Kam <orika@mellanox.com>,
	Raslan Darawsheh <rasland@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: optimize tag traversal with hash list
Date: Fri, 8 Nov 2019 06:38:40 +0000	[thread overview]
Message-ID: <AM4PR05MB32659CE23990D270222B307CD27B0@AM4PR05MB3265.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1573190817-52649-1-git-send-email-bingz@mellanox.com>

> -----Original Message-----
> From: Bing Zhao <bingz@mellanox.com>
> Sent: Friday, November 8, 2019 7:27
> To: Ori Kam <orika@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Raslan Darawsheh <rasland@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] net/mlx5: optimize tag traversal with hash list
> 
> Tag action for flow mark/flag could be reused by different flows.
> When creating a new flow with mark, the existing tag resources will be
> traversed in order to confirm if the action is already created.
> If only one linked list is used, the searching rate will drop significantly with
> the number of tag actions increasing.
> By using a hash lists table, it will speed up the searching process and in the
> meanwhile, the memory consumption won't be large if only a small number
> tag action resources are created(compared to other hash table
> implementations). The list heads array size could be optimized with some
> extendable hash table in the future.
> 
> Signed-off-by: Bing Zhao <bingz@mellanox.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

  reply	other threads:[~2019-11-08  6:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  5:26 Bing Zhao
2019-11-08  6:38 ` Slava Ovsiienko [this message]
2019-11-08 16:09 ` 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=AM4PR05MB32659CE23990D270222B307CD27B0@AM4PR05MB3265.eurprd05.prod.outlook.com \
    --to=viacheslavo@mellanox.com \
    --cc=bingz@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.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).