From: Amir Vadai <amirv.mellanox@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ben Hutchings <ben@decadent.org.uk>,
"David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>,
idos@mellanox.com, Yevgeny Petrilin <yevgenyp@mellanox.com>
Subject: Extend irq_set_affinity_notifier() to use a call chain
Date: Sun, 25 May 2014 15:15:24 +0300 [thread overview]
Message-ID: <5381DEDC.8050204@gmail.com> (raw)
Hi,
I'm working for Mellanox on mlx4_en NIC driver.
We need to be able to be notified on irq affinity changes.
This is because, during non-stop full bandwidth traffic, napi will poll
constantly and no interrupt will be fired. Because of that, even if the
user changes the irq affinity, polling will continue to be done on the
original CPU that was chosen on the first packet.
We would like to be notified when the affinity is changed. When such an
event happen, the driver will arm the interrupts and end the napi
session. An interrupt will start a new napi session on the right CPU.
In order to do that, I need to add a new irq affinity notification
callback (In addition to the existing cpu_rmap notification). For that I
would like to extend irq_set_affinity_notifier() to have a notifier
call-chain instead of a single notifier callback.
I wanted to hear your opinion on this, and unless there is a better
solution, will send an RFC later on.
References:
- http://patchwork.ozlabs.org/patch/65244/ - Review done by Thomas
Glexiber to Ben Hutchings first version of the irq affinity notifiers.
- http://patchwork.ozlabs.org/patch/79593/ - Final version of
irq_set_affinity_notifier() that was applied
Thanks,
Amir
next reply other threads:[~2014-05-25 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 12:15 Amir Vadai [this message]
2014-05-25 13:05 ` Extend irq_set_affinity_notifier() to use a call chain Amir Vadai
2014-05-26 11:15 ` Thomas Gleixner
2014-05-26 11:24 ` Amir Vadai
2014-05-26 11:34 ` Thomas Gleixner
2014-05-26 12:01 ` Amir Vadai
2014-05-26 12:39 ` Thomas Gleixner
2014-05-27 8:15 ` Amir Vadai
2014-05-27 10:10 ` Thomas Gleixner
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=5381DEDC.8050204@gmail.com \
--to=amirv.mellanox@gmail.com \
--cc=amirv@mellanox.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=idos@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=tglx@linutronix.de \
--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).