summaryrefslogtreecommitdiff
path: root/include/linux/timerqueue.h
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-05-01 19:02:09 -0700
committerJakub Kicinski <kuba@kernel.org>2026-05-01 19:02:10 -0700
commit0f19519fdd22bc0f5429377da3a52327c5eee166 (patch)
tree944eb2ffb7b2b7077f9aa8fb5976f2adbebe0127 /include/linux/timerqueue.h
parentff393252f99f261ba885f05fbfdfe89807c7ffd3 (diff)
parentfbf6f64a4322cfeb0d98f39baf8ce18246dd12c0 (diff)
Merge branch 'net-mlx5-enable-sub-page-allocations-for-mlx5_frag_buf'
Tariq Toukan says: ==================== net/mlx5: enable sub-page allocations for mlx5_frag_buf This series aims to improve memory utilization for DMA-coherent fragmented-buffer allocations on systems with large PAGE_SIZE. Before this change, such allocations were page-granular, as they were backed by full pages. On large-page systems this caused significant internal waste for small objects. For example, a single 4K request consumed an entire 64K page. The common kernel solution for sub-page coherent DMA allocations is the DMA pool API. However, those pools do not return pages to the system until teardown. That behavior is not a good fit for mlx5_frag_buf allocations, since they back interface resources (WQs and CQs). Interfaces may be removed dynamically, so their memory footprint should reflect live usage to avoid situations where large amounts of memory remain tied up in pools. This series introduces a lightweight mlx5-local pool implementation for sub-page coherent DMA allocations, which immediately returns free backing pages. It wires mlx5_frag_buf allocations to use these internal pools, while keeping the mechanism reusable for other mlx5-internal coherent DMA allocation users in follow-up work. ==================== Link: https://patch.msgid.link/20260429201429.223809-1-tariqt@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions