diff options
author | 2022-08-04 14:53:07 -0400 | |
---|---|---|
committer | 2022-08-04 14:53:07 -0400 | |
commit | 43fa47cb116daa48f731fa5c00d781200addb2ae (patch) | |
tree | 373e09fb562d1a17710067e0ade6858feabf818e /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | dm verity: only copy bvec_iter in verity_verify_io if in_tasklet (diff) | |
download | wireguard-linux-43fa47cb116daa48f731fa5c00d781200addb2ae.tar.xz wireguard-linux-43fa47cb116daa48f731fa5c00d781200addb2ae.zip |
dm verity: remove WQ_CPU_INTENSIVE flag since using WQ_UNBOUND
The documentation [1] says that WQ_CPU_INTENSIVE is "meaningless" for
unbound wq. So remove WQ_CPU_INTENSIVE from the verify_wq allocation.
1. https://www.kernel.org/doc/html/latest/core-api/workqueue.html#flags
Suggested-by: Maksym Planeta <mplaneta@os.inf.tu-dresden.de>
Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions