From: roszenrami@gmail.com (Rami Rosen)
To: kernelnewbies@lists.kernelnewbies.org
Subject: When to use threaded interrupts?
Date: Thu, 10 Sep 2015 23:09:41 +0300 [thread overview]
Message-ID: <CAKoUArnQL+ExKP2vO0vcAhm=Bgqe8TPDG_efwRnN3M869T4zMA@mail.gmail.com> (raw)
In-Reply-To: <CADxo8WLHWqOkLL0-P+bRJ6J9BEtvXAwfwt1PiVZm1HeNcmTO1A@mail.gmail.com>
Kosta,
Just a wild assumption: maybe the cost of incurring context switches ?
(comparing to tasklets)
Best Regards,
Rami Rosen
http://ramirose.wix.com/ramirosen
On 10 September 2015 at 20:49, Kosta Zertsekel <zertsekel@gmail.com> wrote:
> Hi guys,
>
> I hope I'm on right mailing list. :-)
> I think I get the pro of using threaded interrupts - to decrease the maximum
> interrupt latency on RT workloads and/or RT machines (servers, embedded,
> etc.).
>
> Also, I see that in 4.2 there are only ~76 drivers that use threaded
> interrupt:
> ```
> $ git grep -l IRQ_WAKE_THREAD | sort | grep -v "\.h" | wc -l
> 76
> ```
>
> So, I'd like to ask:
> - Why not **all** of the drivers use the threaded interrupts?
> - What are the cons of the threaded interrupts?
>
> Thanks,
> --- KostaZ
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
next prev parent reply other threads:[~2015-09-10 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 17:49 When to use threaded interrupts? Kosta Zertsekel
2015-09-10 20:09 ` Rami Rosen [this message]
2015-09-13 6:24 ` Kosta Zertsekel
2015-09-13 11:16 ` Rami Rosen
2015-09-15 18:02 ` Kosta Zertsekel
2015-09-15 19:05 ` Greg KH
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='CAKoUArnQL+ExKP2vO0vcAhm=Bgqe8TPDG_efwRnN3M869T4zMA@mail.gmail.com' \
--to=roszenrami@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).