Files
mirror_zfs/module
Mateusz Guzik 09eb36ce3d Introduce CPU_SEQID_UNSTABLE
Current CPU_SEQID users don't care about possibly changing CPU ID, but
enclose it within kpreempt disable/enable in order to fend off warnings
from Linux's CONFIG_DEBUG_PREEMPT.

There is no need to do it. The expected way to get CPU ID while allowing
for migration is to use raw_smp_processor_id.

In order to make this future-proof this patch keeps CPU_SEQID as is and
introduces CPU_SEQID_UNSTABLE instead, to make it clear that consumers
explicitly want this behavior.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Ryan Moeller <ryan@iXsystems.com>
Reviewed-by: Matt Macy <mmacy@FreeBSD.org>
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Closes #11142
2020-11-02 11:51:12 -08:00
..
2020-09-02 09:42:12 -07:00
2020-11-02 11:51:12 -08:00
2020-10-27 09:43:36 -07:00
2020-09-02 09:42:12 -07:00
2020-10-31 09:40:08 -07:00
2020-06-10 09:24:15 -07:00
2020-10-02 17:44:10 -07:00
2020-11-02 11:51:12 -08:00
2020-10-30 15:26:10 -07:00
2020-06-10 09:24:15 -07:00
2020-08-20 10:30:06 -07:00
2020-10-08 20:07:10 -07:00