From: Yuval Mintz <Yuval.Mintz@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: [PATCH net-next 0/4] qed*: IOV patch series
Date: Mon, 22 Aug 2016 13:25:08 +0300 [thread overview]
Message-ID: <1471861512-30104-1-git-send-email-Yuval.Mintz@qlogic.com> (raw)
Recent FW [8.10.10.0] enabled us to support sriov interaction
with legacy VF/PF. This patch series adds the necessary driver changes
to utilize this additional compatibility.
In addition, utilize the new FW ability to prevent pause floods by VFs,
and fix a bug that is [mostly] exposed by the added legacy support.
Dave,
Please consider apply this to 'net-next'.
Thanks,
Yuval
Yuval Mintz (4):
qed: Add support for legacy VFs
qed: Prevent VFs from pause flooding
qed*: Add support for VFs over legacy PFs
qed: Change locking scheme for VF channel
drivers/net/ethernet/qlogic/qed/qed_l2.c | 20 ++-
drivers/net/ethernet/qlogic/qed/qed_l2.h | 5 +-
drivers/net/ethernet/qlogic/qed/qed_sriov.c | 110 +++++++++++--
drivers/net/ethernet/qlogic/qed/qed_vf.c | 231 ++++++++++++++++++++-------
drivers/net/ethernet/qlogic/qed/qed_vf.h | 7 +-
drivers/net/ethernet/qlogic/qede/qede.h | 2 +
drivers/net/ethernet/qlogic/qede/qede_main.c | 10 ++
include/linux/qed/qed_eth_if.h | 3 +
8 files changed, 309 insertions(+), 79 deletions(-)
--
1.9.3
next reply other threads:[~2016-08-22 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 10:25 Yuval Mintz [this message]
2016-08-22 10:25 ` [PATCH net-next 1/4] qed: Add support for legacy VFs Yuval Mintz
2016-08-22 10:25 ` [PATCH net-next 2/4] qed: Prevent VFs from pause flooding Yuval Mintz
2016-08-22 10:25 ` [PATCH net-next 3/4] qed*: Add support for VFs over legacy PFs Yuval Mintz
2016-08-22 10:25 ` [PATCH net-next 4/4] qed: Change locking scheme for VF channel Yuval Mintz
2016-08-23 1:28 ` [PATCH net-next 0/4] qed*: IOV patch series 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=1471861512-30104-1-git-send-email-Yuval.Mintz@qlogic.com \
--to=yuval.mintz@qlogic.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).