From: David Miller <davem@davemloft.net>
To: amirv@mellanox.com
Cc: ogerlitz@mellanox.com, netdev@vger.kernel.org,
yevgenyp@mellanox.com, yuvala@mellanox.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next V6 0/2] cpumask,net: Affinity hint helper function
Date: Sun, 01 Jun 2014 19:17:37 -0700 (PDT) [thread overview]
Message-ID: <20140601.191737.1821014891784987464.davem@davemloft.net> (raw)
In-Reply-To: <1401029247-15196-1-git-send-email-amirv@mellanox.com>
From: Amir Vadai <amirv@mellanox.com>
Date: Sun, 25 May 2014 17:47:25 +0300
> This patchset will set affinity hint to influence IRQs to be allocated on the
> same NUMA node as the one where the card resides. As discussed in
> http://www.spinics.net/lists/netdev/msg271497.html
>
> If the number of IRQs allocated is greater than the number of local NUMA cores, all
> local cores will be used first, and the rest of the IRQs will be on a remote
> NUMA node.
> If no NUMA support - IRQ's and cores will be mapped 1:1
>
> Since the utility function to calculate the mapping could be useful in other mq
> drivers in the kernel, it was added to cpumask.[ch]
>
> This patchset was tested and applied on top of net-next since the first
> consumer is a network device (mlx4_en). Over commit 506724c: "tg3: Override
> clock, link aware and link idle mode during NVRAM dump"
>
> I couldn't find a maintainer for cpumask.c, so only added the kernel mailing
> list
Applied to net-next, thanks.
prev parent reply other threads:[~2014-06-02 2:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 14:47 [PATCH net-next V6 0/2] cpumask,net: Affinity hint helper function Amir Vadai
2014-05-25 14:47 ` [PATCH net-next V6 1/2] cpumask: Utility function to set n'th cpu - local cpu first Amir Vadai
2014-05-27 19:24 ` David Miller
2014-05-28 5:49 ` Or Gerlitz
2014-05-25 14:47 ` [PATCH net-next V6 2/2] net/mlx4_en: Use affinity hint Amir Vadai
2014-06-02 4:16 ` Eric Dumazet
2014-06-02 4:37 ` Eric Dumazet
2014-06-02 4:56 ` David Miller
2014-06-02 5:13 ` Eric Dumazet
2014-06-02 7:10 ` David Miller
2014-06-02 14:08 ` Amir Vadai
2014-06-02 4:54 ` David Miller
2014-06-02 2:17 ` David Miller [this message]
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=20140601.191737.1821014891784987464.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yevgenyp@mellanox.com \
--cc=yuvala@mellanox.com \
/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).