Netdev List
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Matan Barak <matanb@mellanox.com>,
	Amir Vadai <amirv@mellanox.com>,
	Jack Morgenstein <jackm@dev.mellanox.co.il>,
	Or Gerlitz <ogerlitz@mellanox.com>
Subject: [PATCH net-next 0/7] mlx4: Flexible (asymmetric) allocation of EQs and MSI-X vectors
Date: Thu, 13 Nov 2014 14:45:26 +0200	[thread overview]
Message-ID: <1415882733-3084-1-git-send-email-ogerlitz@mellanox.com> (raw)

Hi Dave,

This series from Matan Barak is built as follows:

The 1st two patches fix small bugs w.r.t firmware spec. Next
are two patches which do more re-factoring of the init/fini flow
and a patch that adds support for the QUERY_FUNC firmware command,
these are all pre-steps for the major patch of the series. In this
patch (#6) we change the order of talking/querying the firmware
and enabling SRIOV. This allows to remote worst-case assumption
w.r.t the number of available MSI-X vectors and EQs per function.

The last patch easily enjoys this ordering change, to enable
supports > 64 VFs over a firmware that allows for that.

Or.


Matan Barak (7):
  net/mlx4_core: Fix wrong reading of reserved_eqs
  net/mlx4_core: Use correct variable type for mlx4_slave_cap
  net/mlx4_core: Refactor mlx4_cmd_init and mlx4_cmd_cleanup
  net/mlx4_core: Refactor mlx4_load_one
  net/mlx4_core: Add QUERY_FUNC firmware command
  net/mlx4_core: Flexible (asymmetric) allocation of EQs and MSI-X vectors for PF/VFs
  net/mlx4_core: Support more than 64 VFs

 drivers/infiniband/hw/mlx4/main.c            |    3 +-
 drivers/net/ethernet/mellanox/mlx4/cmd.c     |   76 ++++---
 drivers/net/ethernet/mellanox/mlx4/eq.c      |    8 +-
 drivers/net/ethernet/mellanox/mlx4/fw.c      |  113 +++++++++-
 drivers/net/ethernet/mellanox/mlx4/fw.h      |   15 ++-
 drivers/net/ethernet/mellanox/mlx4/main.c    |  307 +++++++++++++++++++++-----
 drivers/net/ethernet/mellanox/mlx4/mlx4.h    |   11 +-
 drivers/net/ethernet/mellanox/mlx4/profile.c |   19 +-
 include/linux/mlx4/device.h                  |    7 +-
 9 files changed, 440 insertions(+), 119 deletions(-)

             reply	other threads:[~2014-11-13 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 12:45 Or Gerlitz [this message]
2014-11-13 12:45 ` [PATCH net-next 1/7] net/mlx4_core: Fix wrong reading of reserved_eqs Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 2/7] net/mlx4_core: Use correct variable type for mlx4_slave_cap Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 3/7] net/mlx4_core: Refactor mlx4_cmd_init and mlx4_cmd_cleanup Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 4/7] net/mlx4_core: Refactor mlx4_load_one Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 5/7] net/mlx4_core: Add QUERY_FUNC firmware command Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 6/7] net/mlx4_core: Flexible (asymmetric) allocation of EQs and MSI-X vectors for PF/VFs Or Gerlitz
2014-11-13 12:45 ` [PATCH net-next 7/7] net/mlx4_core: Support more than 64 VFs Or Gerlitz
2014-11-13 20:16 ` [PATCH net-next 0/7] mlx4: Flexible (asymmetric) allocation of EQs and MSI-X vectors David Miller

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=1415882733-3084-1-git-send-email-ogerlitz@mellanox.com \
    --to=ogerlitz@mellanox.com \
    --cc=amirv@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=jackm@dev.mellanox.co.il \
    --cc=matanb@mellanox.com \
    --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