aboutsummaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/progs/test_prog_array_init.c
diff options
context:
space:
mode:
authorIlias Apalodimas <[email protected]>2023-02-18 00:21:30 +0200
committerJakub Kicinski <[email protected]>2023-02-21 09:15:39 -0800
commit4d4266e3fd321fadb628ce02de641b129522c39c (patch)
tree3a3b01a058c6b6deb48ef8f14630d1eae7bef589 /tools/testing/selftests/bpf/progs/test_prog_array_init.c
parenta00da30c052f07d67da56efd6a4f1fc85956c979 (diff)
page_pool: add a comment explaining the fragment counter usage
When reading the page_pool code the first impression is that keeping two separate counters, one being the page refcnt and the other being fragment pp_frag_count, is counter-intuitive. However without that fragment counter we don't know when to reliably destroy or sync the outstanding DMA mappings. So let's add a comment explaining this part. Reviewed-by: Alexander Duyck <[email protected]> Signed-off-by: Ilias Apalodimas <[email protected]> Acked-by: Jesper Dangaard Brouer <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/progs/test_prog_array_init.c')
0 files changed, 0 insertions, 0 deletions