summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-10-15 17:14:32 -0700
committerJakub Kicinski <kuba@kernel.org>2026-10-15 17:14:32 -0700
commit97283328376e6ea09940807c52f0096ba305e763 (patch)
tree2229d71bc2bf41ed8eb000998eee6e8bf20d1d61 /scripts
parent0d20963e0aeb39da919288a3b70ecf555f5ab3a1 (diff)
parentb35ec0d877f5ec9e127ca12afbb34883787b7d40 (diff)
Merge branch 'net-netmem-document-design-principles-and-intended-direction'
Mina Almasry says: ==================== net: netmem: document design principles and intended direction Because the networking stack and drivers are only partially converted to netmem_ref and current memory providers only supply unreadable net_iovs, automated code review and analysis tools (such as LLMs) frequently infer the wrong architectural invariants from existing code. Specifically, they often assume that page_pool's struct page APIs are primary rather than legacy wrappers, that memory providers always imply net_iov, that net_iov is inherently unreadable, or that callers should branch on or downcast netmem_ref directly. Document the intended netmem, memory provider, page_pool, and skb fragment design principles concisely in the relevant headers, code comments, and netmem documentation so both developers and automated tools follow the intended abstractions. This series adds comments and documentation rather than performing a large refactor all at once, so that future incremental changes nudge the codebase in the intended direction. This reflects my mental model of the netmem, page_pool, and memory provider architecture; I welcome feedback and disagreements, particularly from major contributors to page_pool and memory providers. ==================== Link: https://patch.msgid.link/20261010033630.1171692-1-almasrymina@google.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions