diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-09-16 15:03:14 +0300 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2026-09-22 12:40:31 +0200 |
| commit | 91e4448b300a97422f0233d6273649d912c1e741 (patch) | |
| tree | 42427999e03b19fc48e8681e5a67da724db7a863 /tools/perf/scripts/python/stackcollapse.py | |
| parent | db111020cc720a39480f67b9bb8308dd7c0c7099 (diff) | |
| download | linux-91e4448b300a97422f0233d6273649d912c1e741.tar.gz linux-91e4448b300a97422f0233d6273649d912c1e741.zip | |
s390/idals: Use kmalloc() for IDAL data buffers
idal_buffer_alloc() allocates the data chunks of an IDAL buffer that is
used for channel I/O.
These buffers can be allocated with kmalloc() as there's nothing special
about them to go directly to the page allocator.
kmalloc() provides a better API that does not require ugly casts and
kfree() does not need to know the size of the freed object.
Performance difference between kmalloc() and __get_free_pages() is not
measurable as both allocators take an object/page from a per-CPU list for
fast path allocations.
For the slow path the performance is anyway determined by the amount of
reclaim involved rather than by what allocator is used.
Replace use of __get_free_pages() with kmalloc() and free_pages() with
kfree().
While on it, tell kmemleak to ignore the data chunks as only their DMA
addresses are retained in the IDAL buffer.
Link: https://lore.kernel.org/all/635405e4-9423-4a25-a6e7-e03c8ea0bcbe@redhat.com
Assisted-by: copilot:claude-opus
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Reviewed-by: Peter Oberparleiter <oberpar@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
