linux-kernel - Re: [PATCH] backing-dev: use synchronize_rcu_expedited instead of synchronize

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 02 Feb 2012 22:59:04 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Mikulas Patocka <mpatocka@...hat.com>
Cc:	axboe@...nel.dk, "Alasdair G. Kergon" <agk@...hat.com>,
	dm-devel@...hat.com, linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ibm.com>
Subject: Re: [PATCH] backing-dev: use synchronize_rcu_expedited instead of
 synchronize_rcu

On Thu, 2012-02-02 at 15:43 -0500, Mikulas Patocka wrote:
> Do you have some measurable use case where the user is removing block 
> devices so heavily that this causes a problem? 

Even one can be a problem, we're having people spend lots of time and
effort to reduce machine wide jitter and interference. Adding it with
such disregard isn't cool.

There's no reason a management cpu adding or removing block devices
should perturb the high-freq trading or industrial laser control running
on the other side of the machine.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/