From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net-next 00/15] Mellanox, mlx5 tc flow handling for concurrent execution (Part 2)
Date: Fri, 09 Aug 2019 20:11:52 -0700 (PDT) [thread overview]
Message-ID: <20190809.201152.259218526870781824.davem@davemloft.net> (raw)
In-Reply-To: <20190809220359.11516-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Fri, 9 Aug 2019 22:04:17 +0000
> This series, mostly from Vlad, is the 2nd part of 3 part series to
> improve mlx5 tc flow handling by removing dependency on rtnl_lock and
> providing a more fine-grained locking and rcu safe data structures to
> allow tc flow handling for concurrent execution.
>
> In this part Vlad handles hairpin, header rewrite and encapsulation
> offloads.
>
> For more information please see tag log below.
>
> Please pull and let me know if there is any problem.
Looks good, pulled, thanks.
prev parent reply other threads:[~2019-08-10 3:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 22:04 [pull request][net-next 00/15] Mellanox, mlx5 tc flow handling for concurrent execution (Part 2) Saeed Mahameed
2019-08-09 22:04 ` [net-next 01/15] net/mlx5e: Extend hairpin entry with reference counter Saeed Mahameed
2019-08-09 22:04 ` [net-next 02/15] net/mlx5e: Protect hairpin entry flows list with spinlock Saeed Mahameed
2019-08-09 22:04 ` [net-next 03/15] net/mlx5e: Protect hairpin hash table with mutex Saeed Mahameed
2019-08-09 22:04 ` [net-next 04/15] net/mlx5e: Allow concurrent creation of hairpin entries Saeed Mahameed
2019-08-09 22:04 ` [net-next 05/15] net/mlx5e: Extend mod header entry with reference counter Saeed Mahameed
2019-08-09 22:04 ` [net-next 06/15] net/mlx5e: Protect mod header entry flows list with spinlock Saeed Mahameed
2019-08-09 22:04 ` [net-next 07/15] net/mlx5e: Protect mod_hdr hash table with mutex Saeed Mahameed
2019-08-09 22:04 ` [net-next 08/15] net/mlx5e: Allow concurrent creation of mod_hdr entries Saeed Mahameed
2019-08-09 22:04 ` [net-next 09/15] net/mlx5e: Extend encap entry with reference counter Saeed Mahameed
2019-08-09 22:04 ` [net-next 10/15] net/mlx5e: Protect encap hash table with mutex Saeed Mahameed
2019-08-09 22:04 ` [net-next 11/15] net/mlx5e: Allow concurrent creation of encap entries Saeed Mahameed
2019-08-09 22:04 ` [net-next 12/15] net/mlx5: E-switch, Removed unused hwid Saeed Mahameed
2019-08-09 22:04 ` [net-next 13/15] net/mlx5e: Simplify querying port representor parent id Saeed Mahameed
2019-08-09 22:04 ` [net-next 14/15] net/mlx5e: Use vhca_id in generating representor port_index Saeed Mahameed
2019-08-09 22:04 ` [net-next 15/15] net/mlx5e: Use refcount_t for refcount Saeed Mahameed
2019-08-10 3:11 ` David Miller [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=20190809.201152.259218526870781824.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).