| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Dec 2017 18:00:05 +0100
From: Mike Galbraith <efault@....de>
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Jeff Layton <jlayton@...nel.org>, linux-nfs@...r.kernel.org
Subject: Re: NFS: 82ms wakeup latency 4.14-rc4
On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote:
>
> Like I say, I don't really understand the issues here, so it's more a
> question than an objection.... (I don't know any reason a
> cond_resched() would be bad there.)
Think of it this way: what all can be queued up behind that kworker
that is hogging CPU for huge swaths of time? It's not only userspace
that suffers.
-Mike
Powered by blists - more mailing lists