From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Hans Ulli Kroll <linux@ulli-kroll.de>,
Larry Finger <Larry.Finger@lwfinger.net>,
Tim K <tpkuester@gmail.com>, "Alex G ." <mr.nuke.me@gmail.com>,
Nick Morrow <morrownr@gmail.com>,
Viktor Petrenko <g0000ga@gmail.com>,
Andreas Henriksson <andreas@fatal.se>,
ValdikSS <iam@valdikss.org.ru>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"petter@technux.se" <petter@technux.se>
Subject: Re: [PATCH] wifi: rtw88: usb: silence log flooding error message
Date: Fri, 26 May 2023 11:33:19 +0200 [thread overview]
Message-ID: <20230526093319.GR17518@pengutronix.de> (raw)
In-Reply-To: <290b05447cc542a9b35c25ff89ba8ff3@realtek.com>
On Thu, May 25, 2023 at 12:45:23AM +0000, Ping-Ke Shih wrote:
>
>
> > -----Original Message-----
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> > Sent: Wednesday, May 24, 2023 6:40 PM
> > To: linux-wireless <linux-wireless@vger.kernel.org>
> > Cc: Hans Ulli Kroll <linux@ulli-kroll.de>; Larry Finger <Larry.Finger@lwfinger.net>; Ping-Ke Shih
> > <pkshih@realtek.com>; Tim K <tpkuester@gmail.com>; Alex G . <mr.nuke.me@gmail.com>; Nick Morrow
> > <morrownr@gmail.com>; Viktor Petrenko <g0000ga@gmail.com>; Andreas Henriksson <andreas@fatal.se>;
> > ValdikSS <iam@valdikss.org.ru>; kernel@pengutronix.de; petter@technux.se; Sascha Hauer
> > <s.hauer@pengutronix.de>
> > Subject: [PATCH] wifi: rtw88: usb: silence log flooding error message
> >
> > When receiving more rx packets than the kernel can handle the driver
> > drops the packets and issues an error message.
>
> The workqueue rtw88_usb is using is:
>
> rtwusb->rxwq = create_singlethread_workqueue("rtw88_usb: rx wq");
>
> Have you tried workqueue with flags WQ_UNBOUND and WQ_HIGHPRI? Like,
>
> rtwusb->rxwq = alloc_workqueue("rtw88_usb: rx wq", WQ_UNBOUND | WQ_HIGHPRI, 0);
> or
> rtwusb->rxwq = alloc_ordered_workqueue("rtw88_usb: rx wq", WQ_HIGHPRI);
>
> Then, driver get more time to process RX, so it could ease flooding messages.
No, I haven't tried this. Regardless of that, I think it still makes
sense to rate limit the messages. There will always be a slower system
that can't cope with the number of packets even with a higher priority
workqueue.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-05-26 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:39 [PATCH] wifi: rtw88: usb: silence log flooding error message Sascha Hauer
2023-05-24 11:34 ` Simon Horman
2023-05-26 10:17 ` Sascha Hauer
2023-05-30 19:59 ` Simon Horman
2023-05-25 0:45 ` Ping-Ke Shih
2023-05-26 9:33 ` Sascha Hauer [this message]
2023-05-26 11:34 ` Ping-Ke Shih
2023-05-27 8:31 ` Kalle Valo
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=20230526093319.GR17518@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Larry.Finger@lwfinger.net \
--cc=andreas@fatal.se \
--cc=g0000ga@gmail.com \
--cc=iam@valdikss.org.ru \
--cc=kernel@pengutronix.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@ulli-kroll.de \
--cc=morrownr@gmail.com \
--cc=mr.nuke.me@gmail.com \
--cc=petter@technux.se \
--cc=pkshih@realtek.com \
--cc=tpkuester@gmail.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;
as well as URLs for NNTP newsgroup(s).