From: Stefan Assmann <sassmann@kpanic.de>
To: intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, davem@davemloft.net,
jeffrey.t.kirsher@intel.com, sassmann@kpanic.de
Subject: [PATCH net-next 0/3] i40e: fix MSI-X vector allocation for > 128 CPU threads
Date: Mon, 19 Sep 2016 13:37:48 +0200 [thread overview]
Message-ID: <1474285071-28218-1-git-send-email-sassmann@kpanic.de> (raw)
Stefan Assmann (3):
i40e: check if vectors are already depleted when doing VMDq allocation
i40e: fix MSI-X vector redistribution if hw limit is reached
i40e: fix sideband flow director vector allocation
drivers/net/ethernet/intel/i40e/i40e_main.c | 76 ++++++++++++++++++-----------
1 file changed, 47 insertions(+), 29 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-19 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 11:37 Stefan Assmann [this message]
2016-09-19 11:37 ` [PATCH net-next 1/3] i40e: check if vectors are already depleted when doing VMDq allocation Stefan Assmann
2016-09-19 11:37 ` [PATCH net-next 2/3] i40e: fix MSI-X vector redistribution if hw limit is reached Stefan Assmann
2016-09-19 11:37 ` [PATCH net-next 3/3] i40e: fix sideband flow director vector allocation Stefan Assmann
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=1474285071-28218-1-git-send-email-sassmann@kpanic.de \
--to=sassmann@kpanic.de \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.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).