From: John Garry <john.garry@huawei.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Marc Zyngier <maz@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
chenxiang <chenxiang66@hisilicon.com>
Subject: Re: About irq_create_affinity_masks() for a platform device driver
Date: Wed, 22 Jan 2020 11:27:50 +0000 [thread overview]
Message-ID: <4b447127-737e-a729-4dc7-82fc8b68af77@huawei.com> (raw)
In-Reply-To: <87o8uveoye.fsf@nanos.tec.linutronix.de>
On 22/01/2020 10:59, Thomas Gleixner wrote:
Hi Thomas,
> John Garry <john.garry@huawei.com> writes:
>> Would there be any issue with a SCSI platform device driver referencing
>> this function?
>>
>> So I have a multi-queue platform device, and I want to spread interrupts
>> over all possible CPUs, just like we can do for PCI MSI vectors. This
>> topic was touched on in [0].
>>
>> And, if so it's ok, could we export that same symbol?
>
> I think you will need something similar to what we have in the pci/msi
> code, but that shouldn't be in your device driver. So I'd rather create
> platform infrastructure for this and export that.
>
That would seem the proper thing do to.
So I was doing this for legacy hw as a cheap and quick performance
boost, but I doubt how many other users there would be in future for any
new API. Also, the effort could be more than the reward and so I may
consider dropping the whole idea.
But I'll have a play with how the code could look now.
Cheers,
john
next prev parent reply other threads:[~2020-01-22 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 10:09 John Garry
2020-01-22 10:59 ` Thomas Gleixner
2020-01-22 11:27 ` John Garry [this message]
2020-01-31 14:25 ` John Garry
2020-01-31 21:41 ` Thomas Gleixner
2020-02-03 15:00 ` John Garry
2020-02-04 9:20 ` Thomas Gleixner
2020-02-04 9:55 ` John Garry
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=4b447127-737e-a729-4dc7-82fc8b68af77@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®