From: Davidlohr Bueso <dave@stgolabs.net>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: rob.rice@broadcom.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH] mailbox: bcm: Replace tasklet with threaded irq
Date: Thu, 14 Jan 2021 19:53:27 -0800 [thread overview]
Message-ID: <20210115035327.xckiigalv3qps7ke@offworld> (raw)
In-Reply-To: <CABb+yY381GYcfAkLuzSTvNz2yHGs4Ap7Kgwiy9r0pXGGQt+ozg@mail.gmail.com>
On Thu, 14 Jan 2021, Jassi Brar wrote:
>On Thu, Jan 14, 2021 at 6:21 PM Davidlohr Bueso <dave@stgolabs.net> wrote:
>>
>> Tasklets have long been deprecated as being too heavy on the system
>> by running in irq context - and this is not a performance critical
>> path. If a higher priority process wants to run, it must wait for
>> the tasklet to finish before doing so.
>>
>> Use a more suitable alternative such as threaded irqs and do the
>> async work in process context.
>>
>> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
>> ---
>Please cc the author and other contributors to this file, esp when
>this is vendor specific code.
So looking at who to Cc I noticed:
commit 8aef00f090bcbe5237c5a6628e7c000890267efe
Author: Rob Rice <rob.rice@broadcom.com>
Date: Mon Nov 14 13:26:01 2016 -0500
mailbox: bcm-pdc: Convert from threaded IRQ to tasklet
Previously used threaded IRQs in the PDC driver to defer
processing the rx DMA ring after getting an rx done interrupt.
Instead, use a tasklet at normal priority for deferred processing.
... which is exactly the opposite of what modern Linux should be
doing. Rob, could this not be done in process context?
Thanks,
Davidlohr
next prev parent reply other threads:[~2021-01-15 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 0:21 Davidlohr Bueso
2021-01-15 1:23 ` Jassi Brar
2021-01-15 3:53 ` Davidlohr Bueso [this message]
2021-01-15 21:55 ` Rob Rice
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=20210115035327.xckiigalv3qps7ke@offworld \
--to=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.rice@broadcom.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
all inboxes | Powered by JetHome®