netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org, valex@mellanox.com, erezsh@mellanox.com
Subject: Re: [pull request][net-next V2 00/18] Mellanox, mlx5 software managed steering
Date: Tue, 03 Sep 2019 21:48:36 -0700 (PDT)	[thread overview]
Message-ID: <20190903.214836.182971744584710402.davem@davemloft.net> (raw)
In-Reply-To: <20190903200409.14406-1-saeedm@mellanox.com>

From: Saeed Mahameed <saeedm@mellanox.com>
Date: Tue, 3 Sep 2019 20:04:24 +0000

> This series adds the support for software (driver managed) flow steering.
> For more information please see tag log below.
> 
> Please pull and let me know if there is any problem.
> 
> Please note that the series starts with a merge of mlx5-next branch,
> to resolve and avoid dependency with rdma tree.
> 
> v2:
>  - Improve return values transformation of the first patch.

Pulled, thanks Saeed.

      parent reply	other threads:[~2019-09-04  4:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 20:04 [pull request][net-next V2 00/18] Mellanox, mlx5 software managed steering Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 01/18] net/mlx5: Add flow steering actions to fs_cmd shim layer Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 02/18] net/mlx5: DR, Add the internal direct rule types definitions Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 03/18] net/mlx5: DR, Add direct rule command utilities Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 04/18] net/mlx5: DR, ICM pool memory allocator Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 05/18] net/mlx5: DR, Expose an internal API to issue RDMA operations Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 06/18] net/mlx5: DR, Add Steering entry (STE) utilities Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 07/18] net/mlx5: DR, Expose steering domain functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 08/18] net/mlx5: DR, Expose steering table functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 09/18] net/mlx5: DR, Expose steering matcher functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 10/18] net/mlx5: DR, Expose steering action functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 11/18] net/mlx5: DR, Expose steering rule functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 12/18] net/mlx5: DR, Add required FW steering functionality Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 13/18] net/mlx5: DR, Expose APIs for direct rule managing Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 14/18] net/mlx5: DR, Add CONFIG_MLX5_SW_STEERING for software steering support Saeed Mahameed
2019-09-03 20:04 ` [net-next V2 15/18] net/mlx5: Add direct rule fs_cmd implementation Saeed Mahameed
2019-09-03 20:05 ` [net-next V2 16/18] net/mlx5: Add API to set the namespace steering mode Saeed Mahameed
2019-09-03 20:05 ` [net-next V2 17/18] net/mlx5: Add support to use SMFS in switchdev mode Saeed Mahameed
2019-09-03 20:05 ` [net-next V2 18/18] net/mlx5: Add devlink flow_steering_mode parameter Saeed Mahameed
2019-09-04  4:48 ` 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=20190903.214836.182971744584710402.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=erezsh@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.com \
    --cc=valex@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).