diff options
| author | Mike Rapoport (Microsoft) <rppt@kernel.org> | 2026-07-04 09:13:37 +0300 |
|---|---|---|
| committer | Martin K. Petersen (Oracle) <mkp@kernel.org> | 2026-09-01 22:31:03 -0400 |
| commit | e64b8f3224add21f02c5d64e11371830e631cdba (patch) | |
| tree | fc33ba24207f6137514a5145b5d2244a86050763 /scripts/Makefile.thinlto | |
| parent | 0abe3fb1c5056b7f2f99178b23db8aa95dd03f85 (diff) | |
| download | linux-next-e64b8f3224add21f02c5d64e11371830e631cdba.tar.gz linux-next-e64b8f3224add21f02c5d64e11371830e631cdba.zip | |
scsi: sym53c8xx_2: Replace __get_free_pages() with kmalloc()
sym53c8xx_2 driver has an internal memory allocator for small
allocations of the driver structures. The backing memory for that
allocator is allocated with __get_free_pages().
This memory can be allocated with kmalloc() as there's nothing special
about it 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().
Link: https://lore.kernel.org/all/635405e4-9423-4a25-a6e7-e03c8ea0bcbe@redhat.com
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Link: https://patch.msgid.link/20260704-b4-scsi-v2-4-7d2d21a810de@kernel.org
Signed-off-by: Martin K. Petersen (Oracle) <mkp@kernel.org>
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
