summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorSergey Senozhatsky <senozhatsky@chromium.org>2025-03-03 11:03:25 +0900
committerAndrew Morton <akpm@linux-foundation.org>2025-03-16 22:06:36 -0700
commitf66140eb71053c0a444421c7f04c7aecc4e31716 (patch)
tree48c9690d9fa89a3054063097ac7fb09238388d45 /tools/perf/scripts/python/exported-sql-viewer.py
parent82f91900c7222c6fae7884da133c5c81dca28d19 (diff)
downloadlinux-f66140eb71053c0a444421c7f04c7aecc4e31716.tar.gz
linux-f66140eb71053c0a444421c7f04c7aecc4e31716.zip
zram: permit reclaim in zstd custom allocator
When configured with pre-trained compression/decompression dictionary support, zstd requires custom memory allocator, which it calls internally from compression()/decompression() routines. That means allocation from atomic context (either under entry spin-lock, or per-CPU local-lock or both). Now, with non-atomic zram read()/write(), those limitations are relaxed and we can allow direct and indirect reclaim. Link: https://lkml.kernel.org/r/20250303022425.285971-17-senozhatsky@chromium.org Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org> Cc: Hillf Danton <hdanton@sina.com> Cc: Kairui Song <ryncsn@gmail.com> Cc: Minchan Kim <minchan@kernel.org> Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Cc: Yosry Ahmed <yosry.ahmed@linux.dev> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions