From: "Tomasz Moń" <tomasz.mon@camlingroup.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>, linux-serial@vger.kernel.org
Cc: Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
k.drobinski@camlintechnologies.com
Subject: Re: [PATCH] serial: imx: reduce RX interrupt frequency
Date: Tue, 4 Jan 2022 12:05:50 +0100 [thread overview]
Message-ID: <4bf9e1dd-e99d-f6ac-ea8b-3796248d9947@camlingroup.com> (raw)
In-Reply-To: <d534d6c2-3f70-3753-62fe-54737ffbe384@pengutronix.de>
On 04.01.2022 11:43, Ahmad Fatoum wrote:
> On 04.01.22 11:32, Tomasz Moń wrote:
>> Triggering RX interrupt for every byte defeats the purpose of aging
>> timer and leads to interrupt starvation at high baud rates.
>
> s/starvation/storm/ ?
Yes, absolutely. While it starves the system, the proper term here is
interrupt storm. Thank you for pointing this out!
Tomasz Mon
next prev parent reply other threads:[~2022-01-04 11:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 10:32 [PATCH] serial: imx: reduce RX interrupt frequency Tomasz Moń
2022-01-04 10:43 ` Ahmad Fatoum
2022-01-04 11:05 ` Tomasz Moń [this message]
2022-01-04 10:54 ` Greg Kroah-Hartman
2022-01-04 11:13 ` Tomasz Moń
2022-01-04 11:38 ` Greg Kroah-Hartman
2022-01-04 22:49 ` Uwe Kleine-König
2022-01-05 7:59 ` Tomasz Moń
2022-01-05 10:37 ` Greg Kroah-Hartman
2022-01-05 10:56 ` Tomasz Moń
2022-01-05 10:57 ` Marc Kleine-Budde
2022-01-06 15:39 ` Sergey Organov
2022-01-05 13:34 ` Sergey Organov
2022-01-06 15:05 ` Uwe Kleine-König
2022-01-10 6:14 ` Tomasz Moń
2022-01-10 8:31 ` Uwe Kleine-König
2022-01-05 13:00 ` Sergey Organov
2022-01-05 13:04 ` Marc Kleine-Budde
2022-01-05 13:37 ` Sergey Organov
2022-01-05 13:40 ` Marc Kleine-Budde
2022-01-05 14:37 ` Sergey Organov
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=4bf9e1dd-e99d-f6ac-ea8b-3796248d9947@camlingroup.com \
--to=tomasz.mon@camlingroup.com \
--cc=a.fatoum@pengutronix.de \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=k.drobinski@camlintechnologies.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-serial@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).