netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: paulb@mellanox.com
Cc: ozsh@mellanox.com, pablo@netfilter.org, majd@mellanox.com,
	roid@mellanox.com, netdev@vger.kernel.org, saeedm@mellanox.com,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] netfilter: flowtable: Support offload of tuples in parallel
Date: Thu, 26 Mar 2020 20:10:48 -0700 (PDT)	[thread overview]
Message-ID: <20200326.201048.137227897330235782.davem@davemloft.net> (raw)
In-Reply-To: <1585055841-14256-1-git-send-email-paulb@mellanox.com>

From: Paul Blakey <paulb@mellanox.com>
Date: Tue, 24 Mar 2020 15:17:18 +0200

> The following patchset opens support for offloading tuples in parallel.
> 
> Patches for netfilter replace the flow table block lock with rw sem,
> and use a work entry per offload command, so they can be run in
> parallel under rw sem read lock.
> 
> MLX5 patch removes the unguarded ct entries list, and instead uses
> rhashtable's iterator to support the above.

This doesn't apply cleanly, please respin.

Thank you.

      parent reply	other threads:[~2020-03-27  3:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 13:17 [PATCH net-next 0/3] netfilter: flowtable: Support offload of tuples in parallel Paul Blakey
2020-03-24 13:17 ` [PATCH net-next 1/3] netfilter: flowtable: Use rw sem as flow block lock Paul Blakey
2020-03-25 20:17   ` Pablo Neira Ayuso
2020-03-24 13:17 ` [PATCH net-next 2/3] netfilter: flowtable: Use work entry per offload command Paul Blakey
2020-03-25 20:18   ` Pablo Neira Ayuso
2020-03-24 13:17 ` [PATCH net-next 3/3] net/mlx5: CT: Use rhashtable's ct entries instead of a seperate list Paul Blakey
2020-03-26  3:53   ` Saeed Mahameed
2020-03-27  3:10 ` 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=20200326.201048.137227897330235782.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=majd@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=ozsh@mellanox.com \
    --cc=pablo@netfilter.org \
    --cc=paulb@mellanox.com \
    --cc=roid@mellanox.com \
    --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).