From: Amir Vadai <amirv.mellanox@gmail.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Yevgeny Petrilin <yevgenyp@mellanox.com>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH net 1/3] net/mlx4_en: Don't use irq_affinity_notifier to track changes in IRQ affinity map
Date: Tue, 24 Jun 2014 10:51:22 +0300 [thread overview]
Message-ID: <53A92DFA.5040302@gmail.com> (raw)
In-Reply-To: <1403534518-20898-2-git-send-email-amirv@mellanox.com>
On 6/23/2014 5:41 PM, Amir Vadai wrote:
> IRQ affinity notifier can only have a single notifier - cpu_rmap
> notifier. Can't use it to track changes in IRQ affinity map.
> Detect IRQ affinity changes by comparing CPU to current IRQ affinity map
> during NAPI poll thread.
>
> Fixes: 2eacc23 ("net/mlx4_core: Enforce irq affinity changes immediatly")
> Signed-off-by: Amir Vadai <amirv@mellanox.com>
Hi,
It seems that this patch will break compilation on s390 architecture.
Please don't pull it - I will do some more work on it and send a V1 of
the patch set.
Amir
next prev parent reply other threads:[~2014-06-24 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 14:41 [PATCH net 0/3] Mellanox EN driver fixes 2014-06-23 Amir Vadai
2014-06-23 14:41 ` [PATCH net 1/3] net/mlx4_en: Don't use irq_affinity_notifier to track changes in IRQ affinity map Amir Vadai
2014-06-24 7:51 ` Amir Vadai [this message]
2014-06-23 14:41 ` [PATCH net 2/3] lib/cpumask: cpumask_set_cpu_local_first to use all cores when numa node is not defined Amir Vadai
2014-06-23 14:41 ` [PATCH net 3/3] net/mlx4_en: IRQ affinity hint is not cleared on port down Amir Vadai
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=53A92DFA.5040302@gmail.com \
--to=amirv.mellanox@gmail.com \
--cc=amirv@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=yevgenyp@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).