From: Sathya Perla <sathya.perla@broadcom.com>
To: netdev@vger.kernel.org
Subject: [net-next PATCH 0/3] be2net: patch set
Date: Mon, 6 Jun 2016 07:22:07 -0400 [thread overview]
Message-ID: <1465212130-510-1-git-send-email-sathya.perla@broadcom.com> (raw)
Hi David, the following patch set contains three non-critical fixes that
can go into the net-next tree.
Patch 1 fixes the logic for provisioning queue pairs on VFs to take into
account the limit on number of TXQs too as in some profiles the number
of TXQs is less than that of RXQs.
Patch 2 enables WoL support from shutdown on Skyhawk.
Patch 3 enhances the logic for provisioning queue pairs on VFs on
SR-IOV over multi-partition configs. Each PF (partition) on a port has to
compute the number of RSS tables it's VFs can use.
thanks!
Somnath Kotur (1):
be2net: Fix provisioning of RSS for VFs in multi-partition
configurations
Sriharsha Basavapatna (1):
be2net: Enable Wake-On-LAN from shutdown for Skyhawk
Suresh Reddy (1):
be2net: use max-TXQs limit too while provisioning VF queue pairs
drivers/net/ethernet/emulex/benet/be.h | 16 +-
drivers/net/ethernet/emulex/benet/be_cmds.c | 147 +++++++++---------
drivers/net/ethernet/emulex/benet/be_cmds.h | 14 +-
drivers/net/ethernet/emulex/benet/be_ethtool.c | 35 ++++-
drivers/net/ethernet/emulex/benet/be_main.c | 203 +++++++++++++++----------
5 files changed, 256 insertions(+), 159 deletions(-)
--
2.4.1
next reply other threads:[~2016-06-06 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 11:22 Sathya Perla [this message]
2016-06-06 11:22 ` [net-next PATCH 1/3] be2net: use max-TXQs limit too while provisioning VF queue pairs Sathya Perla
2016-06-06 11:22 ` [net-next PATCH 2/3] be2net: Enable Wake-On-LAN from shutdown for Skyhawk Sathya Perla
2016-06-06 11:22 ` [net-next PATCH 3/3] be2net: Fix provisioning of RSS for VFs in multi-partition configurations Sathya Perla
2016-06-07 23:19 ` [net-next PATCH 0/3] be2net: patch set 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=1465212130-510-1-git-send-email-sathya.perla@broadcom.com \
--to=sathya.perla@broadcom.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;
as well as URLs for NNTP newsgroup(s).