From: Heiner Kallweit <hkallweit1@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>, Jakub Kicinski <kuba@kernel.org>
Cc: Serge Belyshev <belyshev@depni.sinp.msu.ru>,
David Miller <davem@davemloft.net>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net] r8169: fix operation under forced interrupt threading
Date: Thu, 29 Oct 2020 11:19:14 +0100 [thread overview]
Message-ID: <b976846d-f40e-961f-6a3e-920fd5bf1add@gmail.com> (raw)
In-Reply-To: <87y2jpe5by.fsf@nanos.tec.linutronix.de>
On 29.10.2020 10:42, Thomas Gleixner wrote:
> On Thu, Oct 29 2020 at 09:42, Heiner Kallweit wrote:
>> On 29.10.2020 00:29, Jakub Kicinski wrote:
>>> Other handles may take spin_locks, which will sleep on RT.
>>>
>>> I guess we may need to switch away from the _irqoff() variant for
>>> drivers with IRQF_SHARED after all :(
>>>
>> Right. Unfortunately that's a large number of drivers,
>> e.g. pci_request_irq() sets IRQF_SHARED in general.
>
> IRQF_SHARED is not the problem. It only becomes a problem when the
> interrupt is actually shared which is only the case with the legacy PCI
> interrupt. MSI[X] is not affected at all.
>
Correct, just that the legacy PCI interrupt scenario doesn't affect old
systems/devices only. Users may run the system with nomsi for
whatever reason and we need to be prepared.
We could add handling for (pcidev->msi_enabled || pcidev->msix_enabled),
but this would look somewhat hacky to me.
>> But at least for now there doesn't seem to be a better way to deal
>> with the challenges imposed by forced threading and shared irqs.
>
> We still can do the static key trick, though it's admittedly hacky.
>
> Thanks,
>
> tglx
>
>
next prev parent reply other threads:[~2020-10-29 10:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 16:38 [PATCH net] r8169: fix operation under forced interrupt threading Heiner Kallweit
2020-10-19 23:58 ` Jakub Kicinski
2020-10-28 11:43 ` Serge Belyshev
2020-10-28 12:17 ` Heiner Kallweit
2020-10-28 13:24 ` Thomas Gleixner
2020-10-28 23:29 ` Jakub Kicinski
2020-10-29 8:42 ` Heiner Kallweit
2020-10-29 9:42 ` Thomas Gleixner
2020-10-29 10:19 ` Heiner Kallweit [this message]
2020-10-29 12:25 ` Thomas Gleixner
2020-10-28 14:04 ` Heiner Kallweit
2020-10-28 14:34 ` Serge Belyshev
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=b976846d-f40e-961f-6a3e-920fd5bf1add@gmail.com \
--to=hkallweit1@gmail.com \
--cc=belyshev@depni.sinp.msu.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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;
as well as URLs for NNTP newsgroup(s).