From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] be2net: patch set
Date: Thu, 26 Mar 2015 03:05:07 -0400 [thread overview]
Message-ID: <1427353510-24790-1-git-send-email-sathya.perla@emulex.com> (raw)
Hi David, this patch set includes 2 feature additions to the be2net driver:
Patch 1 sets up cpu affinity hints for be2net irqs using the
cpumask_set_cpu_local_first() API that first picks the near numa cores
and when they are exhausted, selects the far numa cores.
Patch 2 setups up xps queue mapping for be2net's TXQs to avoid,
by default, TX lock contention.
Patch 3 just bumps up the driver version.
Pls consider applying this patch set to the net-next queue. Thanks!
Padmanabh Ratnakar (1):
be2net: assign CPU affinity hints to be2net IRQs
Sathya Perla (2):
be2net: setup xps queue mapping
be2net: bump up the driver version to 10.6.0.1
drivers/net/ethernet/emulex/benet/be.h | 4 +++-
drivers/net/ethernet/emulex/benet/be_main.c | 27 +++++++++++++++++++++------
2 files changed, 24 insertions(+), 7 deletions(-)
--
2.2.0
next reply other threads:[~2015-03-26 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 7:05 Sathya Perla [this message]
2015-03-26 7:05 ` [PATCH net-next 1/3] be2net: assign CPU affinity hints to be2net IRQs Sathya Perla
2015-03-26 7:05 ` [PATCH net-next 2/3] be2net: setup xps queue mapping Sathya Perla
2015-03-26 7:05 ` [PATCH net-next 3/3] be2net: bump up the driver version to 10.6.0.1 Sathya Perla
2015-03-29 19:34 ` [PATCH net-next 0/3] be2net: patch set David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 5:44 Sathya Perla
2015-03-04 20:59 ` David Miller
2014-08-01 12:17 Sathya Perla
2014-08-02 22:59 ` 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=1427353510-24790-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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).