lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Mar 2022 13:21:55 +0000 From: Bryan O'Donoghue <bryan.odonoghue@...aro.org> To: Edmond Gagnon <egagnon@...areup.com>, Kalle Valo <kvalo@...eaurora.org> Cc: Benjamin Li <benl@...areup.com>, Kalle Valo <kvalo@...nel.org>, "David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, wcn36xx@...ts.infradead.org, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2 2/2] wcn36xx: Implement tx_rate reporting On 18/03/2022 19:58, Edmond Gagnon wrote: > + INIT_DELAYED_WORK(&wcn->get_stats_work, wcn36xx_get_stats_work); Instead of forking a worker and polling we could add the relevant SMD command to static int wcn36xx_smd_tx_compl_ind(struct wcn36xx *wcn, void *buf, size_t len) { wcn36xx_smd_get_stats(wcn, 0xSomeMask); } That way we only ever ask for and report a new TX data rate when we know a TX event - and hence a potential TX data-rate update - has taken place. --- bod
Powered by blists - more mailing lists