Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
	Leon Romanovsky <leonro@mellanox.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH mlx5-next 00/16] Mellanox, mlx5 next updates 10-06-2019
Date: Mon, 10 Jun 2019 23:38:11 +0000	[thread overview]
Message-ID: <20190610233733.12155-1-saeedm@mellanox.com> (raw)

Hi All,

This series is aimed mlx5-next branch, it includes a couple of low level
updates for mlx5_core driver, needed for both rdma and net-next trees.

1) Bodong refactors query esw functions so he could use it to support
querying max VFs from device.

2) Vu, handles VF representors creation from VF creation handler
context.

3) Daniel, increased the fw initialization wait timeout for large sriov
configuration.

4) Yuval, refactors IRQ vectors management and separates them from EQs,
so IRQs can be shared between different EQs to save system resources,
especially on VMs and VF functions.

5) Ariel, exploits Yuval's work and uses only one IRQ for the 4 async
EQs we have per function (So we can save 3 IRQ vectors per function).

Thanks,
Saeed.

---

Ariel Levkovich (1):
  net/mlx5: Use a single IRQ for all async EQs

Bodong Wang (2):
  net/mlx5: E-Switch, Return raw output for query esw functions
  net/mlx5: Support querying max VFs from device

Daniel Jurgens (1):
  net/mlx5: Increase wait time for fw initialization

Vu Pham (1):
  net/mlx5: E-Switch, Handle representors creation in handler context

Yuval Avnery (11):
  net/mlx5: Introduce EQ polling budget
  net/mlx5: Change interrupt handler to call chain notifier
  net/mlx5: Separate IRQ request/free from EQ life cycle
  net/mlx5: Separate IRQ data from EQ table data
  net/mlx5: Move IRQ rmap creation to IRQ allocation phase
  net/mlx5: Move IRQ affinity set to IRQ allocation phase
  net/mlx5: Separate IRQ table creation from EQ table creation
  net/mlx5: Generalize IRQ interface to work with irq_table
  net/mlx5: Move all IRQ logic to pci_irq.c
  net/mlx5: Rename mlx5_irq_info to mlx5_irq
  net/mlx5: Add EQ enable/disable API

 drivers/infiniband/hw/mlx5/mlx5_ib.h          |   1 +
 drivers/infiniband/hw/mlx5/odp.c              |  21 +-
 .../net/ethernet/mellanox/mlx5/core/Makefile  |   2 +-
 drivers/net/ethernet/mellanox/mlx5/core/eq.c  | 439 +++++++-----------
 .../net/ethernet/mellanox/mlx5/core/eswitch.c |  33 +-
 .../net/ethernet/mellanox/mlx5/core/eswitch.h |   7 +-
 .../mellanox/mlx5/core/eswitch_offloads.c     |  94 ++--
 .../net/ethernet/mellanox/mlx5/core/lib/eq.h  |   9 +-
 .../net/ethernet/mellanox/mlx5/core/main.c    |  56 ++-
 .../ethernet/mellanox/mlx5/core/mlx5_core.h   |  13 +
 .../net/ethernet/mellanox/mlx5/core/pci_irq.c | 334 +++++++++++++
 .../net/ethernet/mellanox/mlx5/core/sriov.c   |  22 +
 include/linux/mlx5/driver.h                   |  10 +-
 include/linux/mlx5/eq.h                       |  23 +-
 include/linux/mlx5/mlx5_ifc.h                 |   2 +-
 15 files changed, 673 insertions(+), 393 deletions(-)
 create mode 100644 drivers/net/ethernet/mellanox/mlx5/core/pci_irq.c

-- 
2.21.0


             reply	other threads:[~2019-06-10 23:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 23:38 Saeed Mahameed [this message]
2019-06-10 23:38 ` [PATCH mlx5-next 01/16] net/mlx5: Increase wait time for fw initialization Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 02/16] net/mlx5: E-Switch, Handle representors creation in handler context Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 03/16] net/mlx5: E-Switch, Return raw output for query esw functions Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 04/16] net/mlx5: Support querying max VFs from device Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 05/16] net/mlx5: Introduce EQ polling budget Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 06/16] net/mlx5: Change interrupt handler to call chain notifier Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 07/16] net/mlx5: Separate IRQ request/free from EQ life cycle Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 08/16] net/mlx5: Separate IRQ data from EQ table data Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 09/16] net/mlx5: Move IRQ rmap creation to IRQ allocation phase Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 10/16] net/mlx5: Move IRQ affinity set " Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 11/16] net/mlx5: Separate IRQ table creation from EQ table creation Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 12/16] net/mlx5: Generalize IRQ interface to work with irq_table Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 13/16] net/mlx5: Move all IRQ logic to pci_irq.c Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 14/16] net/mlx5: Rename mlx5_irq_info to mlx5_irq Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 15/16] net/mlx5: Use a single IRQ for all async EQs Saeed Mahameed
2019-06-10 23:38 ` [PATCH mlx5-next 16/16] net/mlx5: Add EQ enable/disable API Saeed Mahameed
2019-06-13 18:02 ` [PATCH mlx5-next 00/16] Mellanox, mlx5 next updates 10-06-2019 Saeed Mahameed

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=20190610233733.12155-1-saeedm@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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