From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH net-next RFC 0/3] net: Add support to configure SR-IOV VF queues.
Date: Wed, 9 May 2018 07:21:40 -0400 [thread overview]
Message-ID: <1525864903-32619-1-git-send-email-michael.chan@broadcom.com> (raw)
VF Queue resources are always limited and there is currently no
infrastructure to allow the admin. on the host to add or reduce queue
resources for any particular VF. This RFC series adds the infrastructure
to do that and adds the functionality to the bnxt_en driver.
The "ip link set" command will subsequently be patched to support the new
operation.
Michael Chan (3):
net: Add support to configure SR-IOV VF minimum and maximum queues.
bnxt_en: Store min/max tx/rx rings for individual VFs.
bnxt_en: Implement .ndo_set_vf_queues().
drivers/net/ethernet/broadcom/bnxt/bnxt.c | 1 +
drivers/net/ethernet/broadcom/bnxt/bnxt.h | 5 ++
drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.c | 90 +++++++++++++++++++++++--
drivers/net/ethernet/broadcom/bnxt/bnxt_sriov.h | 2 +
include/linux/if_link.h | 4 ++
include/linux/netdevice.h | 6 ++
include/uapi/linux/if_link.h | 9 +++
net/core/rtnetlink.c | 28 +++++++-
8 files changed, 138 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-05-09 11:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 11:21 Michael Chan [this message]
2018-05-09 11:21 ` [PATCH net-next RFC 1/3] net: Add support to configure SR-IOV VF minimum and maximum queues Michael Chan
2018-05-09 23:15 ` Jakub Kicinski
2018-05-10 0:22 ` Michael Chan
2018-05-10 1:10 ` Jakub Kicinski
2018-05-10 2:32 ` Michael Chan
2018-05-09 11:21 ` [PATCH net-next RFC 2/3] bnxt_en: Store min/max tx/rx rings for individual VFs Michael Chan
2018-05-09 11:21 ` [PATCH net-next RFC 3/3] bnxt_en: Implement .ndo_set_vf_queues() Michael Chan
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=1525864903-32619-1-git-send-email-michael.chan@broadcom.com \
--to=michael.chan@broadcom.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).