page_pool: recycle buffers
Subsystems (13)
v5 cover page_pool: recycle buffers
From: Matteo Croce <[email protected]>
This is a respin of [1]
This patchset shows the plans for allowing page_pool to handle and maintain DMA map/unmap of the pages it serves to the driver. For this to work a return hook in the network core is introduced.
The overall purpose is to simplify drivers, by providing a page allocation API that does recycling, such that each driver doesn't have to reinvent its own recycling scheme. Using page_pool in a driver does not require implementing XDP support, but it makes it trivially easy to do so. Instead of allocating buffers specifically for SKBs we now allocate a generic buffer and either wrap it on an SKB (via build_skb) or create an XDP frame.
The recycling code leverages the XDP recycle APIs.
The Marvell mvpp2 and mvneta drivers are used in this patchset to demonstrate how to use the API, and tested on a MacchiatoBIN and EspressoBIN boards respectively.
Please let this going in on a future -rc1 so to allow enough time to have wider tests.
Note that this series depends on the change "mm: fix struct page layout on 32-bit systems"[2] which is not yet in master.
v4 -> v5:
- move the signature so it doesn't alias with page->mapping
- use an invalid pointer as magic
- incorporate Matthew Wilcox's changes for pfmemalloc pages
- move the __skb_frag_unref() changes to a preliminary patch
- refactor some cpp directives
- only attempt recycling if skb->head_frag
- clear skb->pp_recycle in pskb_expand_head()
v3 -> v4:
- store a pointer to page_pool instead of xdp_mem_info
- drop a patch which reduces xdp_mem_info size
- do the recycling in the page_pool code instead of xdp_return
- remove some unused headers include
- remove some useless forward declaration
v2 -> v3:
- added missing SOBs
- CCed the MM people
v1 -> v2:
- fix a commit message
- avoid setting pp_recycle multiple times on mvneta
- squash two patches to avoid breaking bisect
[1] https://lore.kernel.org/netdev/154413868810.21735.572808840657728172.stgit@firesoul/
[2] https://lore.kernel.org/linux-mm/[email protected]/
Ilias Apalodimas (1):
page_pool: Allow drivers to hint on SKB recycling
Matteo Croce (4):
mm: add a signature in struct page
skbuff: add a parameter to __skb_frag_unref
mvpp2: recycle buffers
mvneta: recycle buffers
drivers/net/ethernet/marvell/mvneta.c | 11 +++--- .../net/ethernet/marvell/mvpp2/mvpp2_main.c | 17 +++++----- drivers/net/ethernet/marvell/sky2.c | 2 +- drivers/net/ethernet/mellanox/mlx4/en_rx.c | 2 +- include/linux/mm.h | 12 ++++--- include/linux/mm_types.h | 12 +++++++ include/linux/skbuff.h | 34 ++++++++++++++++--- include/net/page_pool.h | 11 ++++++ net/core/page_pool.c | 27 +++++++++++++++ net/core/skbuff.c | 25 +++++++++++--- net/tls/tls_device.c | 2 +- 11 files changed, 126 insertions(+), 29 deletions(-)
Signature · 1 line
2.31.1
PATCH v5 1/5 mm: add a signature in struct page
From: Matteo Croce <[email protected]>
This is needed by the page_pool to avoid recycling a page not allocated via page_pool.
The page->signature field is aliased to page->lru.next and page->compound_head, but it can't be set by mistake because the signature value is a bad pointer, and can't trigger a false positive in PageTail() because the last bit is 0.
--- include/linux/mm.h | 12 +++++++----- include/linux/mm_types.h | 12 ++++++++++++ include/net/page_pool.h | 2 ++ net/core/page_pool.c | 4 ++++ 4 files changed, 25 insertions(+), 5 deletions(-)
include/linux/mm.h +7 -5
@@ -1668,10 +1668,12 @@ struct address_space *page_mapping(struct page *page);static inline bool page_is_pfmemalloc (const struct page *page) {/* -* Page index cannot be this large so this must be -* a pfmemalloc page. +* This is not a tail page; compound_head of a head page is unused +* at return from the page allocator, and will be overwritten +* by callers who do not care whether the page came from the +* reserves. */ -return page->index ==-1UL ; +return page->compound_head &2 ; }/*
@@ -1680,12 +1682,12 @@ static inline bool page_is_pfmemalloc(const struct page *page)*/ static inline void set_page_pfmemalloc (struct page *page) { - page->index =-1UL ; + page->compound_head =2 ; }static inline void clear_page_pfmemalloc (struct page *page) { - page->index =0 ; + page->compound_head =0 ; }/*
include/linux/mm_types.h +12 -0
@@ -96,6 +96,18 @@ struct page {unsigned long private; };struct {/* page_pool used by netstack */ +/** +* @pp_magic: magic value to avoid recycling non +* page_pool allocated pages. +* It aliases with page->lru.next +*/ +unsigned long pp_magic; +/** +* @pp: pointer to page_pool. +* It aliases with page->lru.prev +*/ +struct page_pool *pp; +unsigned long _pp_mapping_pad;/** * @dma_addr: might require a 64-bit value on * 32-bit architectures.
include/net/page_pool.h +2 -0
@@ -63,6 +63,8 @@*/ #define PP_ALLOC_CACHE_SIZE 128#define PP_ALLOC_CACHE_REFILL 64 +#define PP_SIGNATURE (POISON_POINTER_DELTA + 0x40) +struct pp_alloc_cache {u32 count;struct page *cache[PP_ALLOC_CACHE_SIZE ];
net/core/page_pool.c +4 -0
@@ -221,6 +221,8 @@ static struct page *__page_pool_alloc_page_order(struct page_pool *pool,return NULL ; } + page->pp_magic =PP_SIGNATURE ; +/* Track how many pages are held 'in-flight' */ pool->pages_state_hold_cnt++;trace_page_pool_state_hold (pool, page, pool->pages_state_hold_cnt);
@@ -341,6 +343,8 @@ void page_pool_release_page(struct page_pool *pool, struct page *page) DMA_ATTR_SKIP_CPU_SYNC);page_pool_set_dma_addr (page,0 ); skip_dma_unmap: + page->pp_magic =0 ; +/* This may be the last page returned, releasing the pool, so * it is not safe to reference pool afterwards. */
Signature · 1 line
2.31.1
PATCH v5 2/5 skbuff: add a parameter to __skb_frag_unref
In reply to Matteo CroceFrom: Matteo Croce <[email protected]>
This is a prerequisite patch, the next one is enabling recycling of skbs and fragments. Add an extra argument on __skb_frag_unref() to handle recycling, and update the current users of the function with that.
--- drivers/net/ethernet/marvell/sky2.c | 2 +- drivers/net/ethernet/mellanox/mlx4/en_rx.c | 2 +- include/linux/skbuff.h | 8 +++++--- net/core/skbuff.c | 4 ++-- net/tls/tls_device.c | 2 +- 5 files changed, 10 insertions(+), 8 deletions(-)
drivers/net/ethernet/marvell/sky2.c +1 -1
@@ -2503,7 +2503,7 @@ static void skb_put_frags(struct sk_buff *skb, unsigned int hdr_space,if (length ==0 ) {/* don't need this page */ -__skb_frag_unref (frag); +__skb_frag_unref (frag, false); --skb_shinfo (skb)->nr_frags; }else { size =min (length, (unsigned )PAGE_SIZE );
drivers/net/ethernet/mellanox/mlx4/en_rx.c +1 -1
@@ -526,7 +526,7 @@ static int mlx4_en_complete_rx_desc(struct mlx4_en_priv *priv, fail:while (nr >0 ) { nr--; -__skb_frag_unref (skb_shinfo (skb)->frags + nr); +__skb_frag_unref (skb_shinfo (skb)->frags + nr, false); }return 0 ; }
include/linux/skbuff.h +5 -3
@@ -3081,10 +3081,12 @@ static inline void skb_frag_ref(struct sk_buff *skb, int f)/** * __skb_frag_unref - release a reference on a paged fragment. * @frag: the paged fragment +* @recycle: recycle the page if allocated via page_pool * -* Releases a reference on the paged fragment @frag. +* Releases a reference on the paged fragment @frag +* or recycles the page via the page_pool API. */ -static inline void __skb_frag_unref (skb_frag_t *frag) +static inline void __skb_frag_unref (skb_frag_t *frag,bool recycle) {put_page (skb_frag_page (frag)); }
@@ -3098,7 +3100,7 @@ static inline void __skb_frag_unref(skb_frag_t *frag)*/ static inline void skb_frag_unref (struct sk_buff *skb,int f) { -__skb_frag_unref (&skb_shinfo (skb)->frags[f]); +__skb_frag_unref (&skb_shinfo (skb)->frags[f], false); }/**
net/core/skbuff.c +2 -2
@@ -664,7 +664,7 @@ static void skb_release_data(struct sk_buff *skb)skb_zcopy_clear (skb, true);for (i =0 ; i < shinfo->nr_frags; i++) -__skb_frag_unref (&shinfo->frags[i]); +__skb_frag_unref (&shinfo->frags[i], false);if (shinfo->frag_list)kfree_skb_list (shinfo->frag_list);
@@ -3495,7 +3495,7 @@ int skb_shift(struct sk_buff *tgt, struct sk_buff *skb, int shiftlen) fragto = &skb_shinfo (tgt)->frags[merge];skb_frag_size_add (fragto,skb_frag_size (fragfrom)); -__skb_frag_unref (fragfrom); +__skb_frag_unref (fragfrom, false); }/* Reposition in the original skb */
net/tls/tls_device.c +1 -1
@@ -127,7 +127,7 @@ static void destroy_record(struct tls_record_info *record)int i;for (i =0 ; i < record->num_frags; i++) -__skb_frag_unref (&record->frags[i]); +__skb_frag_unref (&record->frags[i], false);kfree (record); }
Signature · 1 line
2.31.1
PATCH v5 3/5 page_pool: Allow drivers to hint on SKB recycling
In reply to Matteo CroceFrom: Ilias Apalodimas <[email protected]>
Up to now several high speed NICs have custom mechanisms of recycling the allocated memory they use for their payloads.
Our page_pool API already has recycling capabilities that are always used when we are running in 'XDP mode'. So let's tweak the API and the kernel network stack slightly and allow the recycling to happen even during the standard operation.
The API doesn't take into account 'split page' policies used by those drivers currently, but can be extended once we have users for that.
The idea is to be able to intercept the packet on skb_release_data(). If it's a buffer coming from our page_pool API recycle it back to the pool for further usage or just release the packet entirely.
To achieve that we introduce a bit in struct sk_buff (pp_recycle:1) and a field in struct page (page->pp) to store the page_pool pointer. Storing the information in page->pp allows us to recycle both SKBs and their fragments.
The SKB bit is needed for a couple of reasons. First of all in an effort to affect the free path as less as possible, reading a single bit, is better that trying to derive identical information for the page stored data. We do have a special mark in the page, that won't allow this to happen, but again deciding without having to read the entire page is preferable.
The driver has to take care of the sync operations on it's own during the buffer recycling since the buffer is, after opting-in to the recycling, never unmapped.
Since the gain on the drivers depends on the architecture, we are not enabling recycling by default if the page_pool API is used on a driver. In order to enable recycling the driver must call skb_mark_for_recycle() to store the information we need for recycling in page->pp and enabling the recycling bit, or page_pool_store_mem_info() for a fragment.
--- include/linux/skbuff.h | 28 +++++++++++++++++++++++++--- include/net/page_pool.h | 9 +++++++++ net/core/page_pool.c | 23 +++++++++++++++++++++++ net/core/skbuff.c | 25 +++++++++++++++++++++---- 4 files changed, 78 insertions(+), 7 deletions(-)
include/linux/skbuff.h +25 -3
@@ -40,6 +40,9 @@#if IS_ENABLED (CONFIG_NF_CONNTRACK )#include <linux/netfilter/nf_conntrack_common.h> #endif +#ifdef CONFIG_PAGE_POOL +#include <net/page_pool.h> +#endif /* The interface for checksum offload between the stack and networking drivers * is as follows...
@@ -667,6 +670,8 @@ typedef unsigned char *sk_buff_data_t;* @head_frag: skb was allocated from page fragments, * not allocated by kmalloc() or vmalloc(). * @pfmemalloc: skbuff was allocated from PFMEMALLOC reserves +* @pp_recycle: mark the packet for recycling instead of freeing (implies +* page_pool support on driver) * @active_extensions: active extensions (skb_ext_id types) * @ndisc_nodetype: router type (from link layer) * @ooo_okay: allow the mapping of a socket to a queue to be changed
@@ -791,10 +796,12 @@ struct sk_buff { fclone:2, peeked:1, head_frag:1, - pfmemalloc:1; + pfmemalloc:1, + pp_recycle:1; /* page_pool recycle indicator */#ifdef CONFIG_SKB_EXTENSIONS __u8 active_extensions;#endif +/* fields enclosed in headers_start/headers_end are copied * using a single memcpy() in __copy_skb_header() */
@@ -3088,7 +3095,13 @@ static inline void skb_frag_ref(struct sk_buff *skb, int f)*/ static inline void __skb_frag_unref (skb_frag_t *frag,bool recycle) { -put_page (skb_frag_page (frag)); +struct page *page =skb_frag_page (frag); + +#ifdef CONFIG_PAGE_POOL +if (recycle &&page_pool_return_skb_page (page_address (page))) +return ; +#endif +put_page (page); }/**
@@ -3100,7 +3113,7 @@ static inline void __skb_frag_unref(skb_frag_t *frag, bool recycle)*/ static inline void skb_frag_unref (struct sk_buff *skb,int f) { -__skb_frag_unref (&skb_shinfo (skb)->frags[f], false); +__skb_frag_unref (&skb_shinfo (skb)->frags[f], skb->pp_recycle); }/**
@@ -4699,5 +4712,14 @@ static inline u64 skb_get_kcov_handle(struct sk_buff *skb)#endif } +#ifdef CONFIG_PAGE_POOL +static inline void skb_mark_for_recycle (struct sk_buff *skb,struct page *page, +struct page_pool *pp) +{ + skb->pp_recycle =1 ; +page_pool_store_mem_info (page, pp); +} +#endif +#endif /* __KERNEL__ */ #endif /* _LINUX_SKBUFF_H */
include/net/page_pool.h +9 -0
@@ -148,6 +148,8 @@ inline enum dma_data_direction page_pool_get_dma_dir(struct page_pool *pool)return pool->p.dma_dir; } +bool page_pool_return_skb_page (void *data); +struct page_pool *page_pool_create (const struct page_pool_params *params);#ifdef CONFIG_PAGE_POOL
@@ -253,4 +255,11 @@ static inline void page_pool_ring_unlock(struct page_pool *pool) spin_unlock_bh(&pool->ring.producer_lock); } +/* Store mem_info on struct page and use it while recycling skb frags */ +static inline +void page_pool_store_mem_info (struct page *page,struct page_pool *pp) +{ + page->pp = pp; +} +#endif /* _NET_PAGE_POOL_H */
net/core/page_pool.c +23 -0
@@ -626,3 +626,26 @@ void page_pool_update_nid(struct page_pool *pool, int new_nid) } }EXPORT_SYMBOL (page_pool_update_nid); + +bool page_pool_return_skb_page (void *data) +{ +struct page_pool *pp; +struct page *page; + + page =virt_to_head_page (data); +if (unlikely (page->pp_magic !=PP_SIGNATURE )) +return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model. +* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ; +page_pool_put_full_page (pp,virt_to_head_page (data), false); + +return true; +} +EXPORT_SYMBOL (page_pool_return_skb_page);
net/core/skbuff.c +21 -4
@@ -70,6 +70,9 @@#include <net/xfrm.h> #include <net/mpls.h> #include <net/mptcp.h> +#ifdef CONFIG_PAGE_POOL +#include <net/page_pool.h> +#endif #include <linux/uaccess.h> #include <trace/events/skb.h>
@@ -645,10 +648,15 @@ static void skb_free_head(struct sk_buff *skb) {unsigned char *head = skb->head; -if (skb->head_frag) +if (skb->head_frag) { +#ifdef CONFIG_PAGE_POOL +if (skb->pp_recycle &&page_pool_return_skb_page (head)) +return ; +#endif skb_free_frag (head); -else + }else {kfree (head); + } }static void skb_release_data (struct sk_buff *skb)
@@ -664,7 +672,7 @@ static void skb_release_data(struct sk_buff *skb)skb_zcopy_clear (skb, true);for (i =0 ; i < shinfo->nr_frags; i++) -__skb_frag_unref (&shinfo->frags[i], false); +__skb_frag_unref (&shinfo->frags[i], skb->pp_recycle);if (shinfo->frag_list)kfree_skb_list (shinfo->frag_list);
@@ -1046,6 +1054,7 @@ static struct sk_buff *__skb_clone(struct sk_buff *n, struct sk_buff *skb) n->nohdr =0 ; n->peeked =0 ;C (pfmemalloc); +C (pp_recycle); n->destructor =NULL ;C (tail);C (end);
@@ -1725,6 +1734,7 @@ int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail, skb->cloned =0 ; skb->hdr_len =0 ; skb->nohdr =0 ; + skb->pp_recycle =0 ;atomic_set (&skb_shinfo (skb)->dataref,1 );skb_metadata_clear (skb);
@@ -3495,7 +3505,7 @@ int skb_shift(struct sk_buff *tgt, struct sk_buff *skb, int shiftlen) fragto = &skb_shinfo (tgt)->frags[merge];skb_frag_size_add (fragto,skb_frag_size (fragfrom)); -__skb_frag_unref (fragfrom, false); +__skb_frag_unref (fragfrom, skb->pp_recycle); }/* Reposition in the original skb */
@@ -5285,6 +5295,13 @@ bool skb_try_coalesce(struct sk_buff *to, struct sk_buff *from,if (skb_cloned (to))return false; +/* We can't coalesce skb that are allocated from slab and page_pool +* The recycle mark is on the skb, so that might end up trying to +* recycle slab allocated skb->head +*/ +if (to->pp_recycle != from->pp_recycle) +return false; +if (len <=skb_tailroom (to)) {if (len)BUG_ON (skb_copy_bits (from,0 ,skb_put (to, len), len));
Signature · 1 line
2.31.1
PATCH v5 4/5 mvpp2: recycle buffers
In reply to Matteo CroceFrom: Matteo Croce <[email protected]>
Use the new recycling API for page_pool.
In a drop rate test, the packet rate is more than doubled, from 962 Kpps to 2047 Kpps.
perf top on a stock system shows:
Overhead Shared Object Symbol 30.67% [kernel] [k] page_pool_release_page 8.37% [kernel] [k] get_page_from_freelist 7.34% [kernel] [k] free_unref_page 6.47% [mvpp2] [k] mvpp2_rx 4.69% [kernel] [k] eth_type_trans 4.55% [kernel] [k] __netif_receive_skb_core 4.40% [kernel] [k] build_skb 4.29% [kernel] [k] kmem_cache_free 4.00% [kernel] [k] kmem_cache_alloc 3.81% [kernel] [k] dev_gro_receive
With packet rate stable at 962 Kpps:
tx: 0 bps 0 pps rx: 477.4 Mbps 962.6 Kpps
tx: 0 bps 0 pps rx: 477.6 Mbps 962.8 Kpps
tx: 0 bps 0 pps rx: 477.6 Mbps 962.9 Kpps
tx: 0 bps 0 pps rx: 477.2 Mbps 962.1 Kpps
tx: 0 bps 0 pps rx: 477.5 Mbps 962.7 Kpps
And this is the same output with recycling enabled:
Overhead Shared Object Symbol 12.75% [mvpp2] [k] mvpp2_rx 9.56% [kernel] [k] __netif_receive_skb_core 9.29% [kernel] [k] build_skb 9.27% [kernel] [k] eth_type_trans 8.39% [kernel] [k] kmem_cache_alloc 7.85% [kernel] [k] kmem_cache_free 7.36% [kernel] [k] page_pool_put_page 6.45% [kernel] [k] dev_gro_receive 4.72% [kernel] [k] __xdp_return 3.06% [kernel] [k] page_pool_refill_alloc_cache
With packet rate above 2000 Kpps:
tx: 0 bps 0 pps rx: 1015 Mbps 2046 Kpps
tx: 0 bps 0 pps rx: 1015 Mbps 2047 Kpps
tx: 0 bps 0 pps rx: 1015 Mbps 2047 Kpps
tx: 0 bps 0 pps rx: 1015 Mbps 2047 Kpps
tx: 0 bps 0 pps rx: 1015 Mbps 2047 Kpps
The major performance increase is explained by the fact that the most CPU consuming functions (page_pool_release_page, get_page_from_freelist and free_unref_page) are no longer called on a per packet basis.
The test was done by sending to the macchiatobin 64 byte ethernet frames with an invalid ethertype, so the packets are dropped early in the RX path.
--- drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c +9 -8
@@ -3847,6 +3847,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,struct mvpp2_pcpu_stats ps = {};enum dma_data_direction dma_dir;struct bpf_prog *xdp_prog; +struct xdp_rxq_info *rxqi;struct xdp_buff xdp;int rx_received;int rx_done =0 ;
@@ -3912,15 +3913,15 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,else frag_size = bm_pool->frag_size; -if (xdp_prog) { -struct xdp_rxq_info *xdp_rxq; +if (bm_pool->pkt_size ==MVPP2_BM_SHORT_PKT_SIZE ) + rxqi = &rxq->xdp_rxq_short; +else + rxqi = &rxq->xdp_rxq_long; -if (bm_pool->pkt_size ==MVPP2_BM_SHORT_PKT_SIZE ) - xdp_rxq = &rxq->xdp_rxq_short; -else - xdp_rxq = &rxq->xdp_rxq_long; +if (xdp_prog) { + xdp.rxq = rxqi; -xdp_init_buff (&xdp,PAGE_SIZE , xdp_rxq); +xdp_init_buff (&xdp,PAGE_SIZE , rxqi);xdp_prepare_buff (&xdp, data,MVPP2_MH_SIZE +MVPP2_SKB_HEADROOM , rx_bytes, false);
@@ -3964,7 +3965,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi, }if (pp) -page_pool_release_page (pp,virt_to_page (data)); +skb_mark_for_recycle (skb,virt_to_page (data), pp);else dma_unmap_single_attrs(dev->dev.parent, dma_addr, bm_pool->buf_size, DMA_FROM_DEVICE,
Signature · 1 line
2.31.1
PATCH v5 5/5 mvneta: recycle buffers
In reply to Matteo CroceFrom: Matteo Croce <[email protected]>
Use the new recycling API for page_pool.
In a drop rate test, the packet rate increased di 10%, from 269 Kpps to 296 Kpps.
perf top on a stock system shows:
Overhead Shared Object Symbol 21.78% [kernel] [k] __pi___inval_dcache_area 21.66% [mvneta] [k] mvneta_rx_swbm 7.00% [kernel] [k] kmem_cache_alloc 6.05% [kernel] [k] eth_type_trans 4.44% [kernel] [k] kmem_cache_free.part.0 3.80% [kernel] [k] __netif_receive_skb_core 3.68% [kernel] [k] dev_gro_receive 3.65% [kernel] [k] get_page_from_freelist 3.43% [kernel] [k] page_pool_release_page 3.35% [kernel] [k] free_unref_page
And this is the same output with recycling enabled:
Overhead Shared Object Symbol 24.10% [kernel] [k] __pi___inval_dcache_area 23.02% [mvneta] [k] mvneta_rx_swbm 7.19% [kernel] [k] kmem_cache_alloc 6.50% [kernel] [k] eth_type_trans 4.93% [kernel] [k] __netif_receive_skb_core 4.77% [kernel] [k] kmem_cache_free.part.0 3.93% [kernel] [k] dev_gro_receive 3.03% [kernel] [k] build_skb 2.91% [kernel] [k] page_pool_put_page 2.85% [kernel] [k] __xdp_return
The test was done with mausezahn on the TX side with 64 byte raw ethernet frames.
--- drivers/net/ethernet/marvell/mvneta.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/net/ethernet/marvell/mvneta.c +7 -4
@@ -2320,7 +2320,7 @@ mvneta_swbm_add_rx_fragment(struct mvneta_port *pp, }static struct sk_buff * -mvneta_swbm_build_skb (struct mvneta_port *pp,struct mvneta_rx_queue *rxq, +mvneta_swbm_build_skb (struct mvneta_port *pp,struct page_pool *pool,struct xdp_buff *xdp,u32 desc_status) {struct skb_shared_info *sinfo =xdp_get_shared_info_from_buff (xdp);
@@ -2331,7 +2331,7 @@ mvneta_swbm_build_skb(struct mvneta_port *pp, struct mvneta_rx_queue *rxq,if (!skb)return ERR_PTR (-ENOMEM ); -page_pool_release_page (rxq->page_pool,virt_to_page (xdp->data)); +skb_mark_for_recycle (skb,virt_to_page (xdp->data), pool);skb_reserve (skb, xdp->data - xdp->data_hard_start);skb_put (skb, xdp->data_end - xdp->data);
@@ -2343,7 +2343,10 @@ mvneta_swbm_build_skb(struct mvneta_port *pp, struct mvneta_rx_queue *rxq,skb_add_rx_frag (skb,skb_shinfo (skb)->nr_frags,skb_frag_page (frag),skb_frag_off (frag),skb_frag_size (frag),PAGE_SIZE ); -page_pool_release_page (rxq->page_pool,skb_frag_page (frag)); +/* We don't need to reset pp_recycle here. It's already set, so +* just mark fragments for recycling. +*/ +page_pool_store_mem_info (skb_frag_page (frag), pool); }return skb;
@@ -2425,7 +2428,7 @@ static int mvneta_rx_swbm(struct napi_struct *napi, mvneta_run_xdp(pp, rxq, xdp_prog, &xdp_buf, frame_sz, &ps)) goto next; - skb =mvneta_swbm_build_skb (pp, rxq, &xdp_buf, desc_status); + skb =mvneta_swbm_build_skb (pp, pp, &xdp_buf, desc_status);if (IS_ERR (skb)) {struct mvneta_pcpu_stats *stats =this_cpu_ptr (pp->stats);
Signature · 1 line
2.31.1
Russell King (Oracle)
maintainerRe: [PATCH net-next v5 4/5] mvpp2: recycle buffers
In reply to Matteo CroceQuoted 29 lines · Matteo Croce
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c +8
-0@@ -3847,6 +3847,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,struct mvpp2_pcpu_stats ps = {};enum dma_data_direction dma_dir;struct bpf_prog *xdp_prog; +struct xdp_rxq_info *rxqi;struct xdp_buff xdp;int rx_received;int rx_done =0 ;@@ -3912,15 +3913,15 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,else frag_size = bm_pool->frag_size; +if (bm_pool->pkt_size ==MVPP2_BM_SHORT_PKT_SIZE ) + rxqi = &rxq->xdp_rxq_short; +else + rxqi = &rxq->xdp_rxq_long; +if (xdp_prog) { + xdp.rxq = rxqi; +xdp_init_buff (&xdp,PAGE_SIZE , rxqi);xdp_prepare_buff (&xdp, data,MVPP2_MH_SIZE +MVPP2_SKB_HEADROOM , rx_bytes, false);
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi, · line 3971
Quoted 7 lines
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c +1
-0@@ -3964,7 +3965,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi, }if (pp) +skb_mark_for_recycle (skb,virt_to_page (data), pp);else dma_unmap_single_attrs(dev->dev.parent, dma_addr, bm_pool->buf_size, DMA_FROM_DEVICE,
Looking at the above, which I've only quoted the _resulting_ code after your patch above, I don't see why you have moved the "bm_pool->pkt_size == MVPP2_BM_SHORT_PKT_SIZE" conditional outside of the test for xdp_prog - I don't see rxqi being used except within that conditional. Please can you explain the reasoning there?
Thanks.
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Re: [PATCH net-next v5 5/5] mvneta: recycle buffers
In reply to Matteo CroceQuoted 4 lines · Matteo Croce
From: Matteo Croce <[email protected]>
Use the new recycling API for
page_pool.
In a drop rate test, the packet rate increased di 10%,
Typo - "by" ?
Quoted 30 lines
from 269 Kpps to 296 Kpps.
perf top on a stock system shows:
Overhead Shared Object Symbol 21.78% [kernel] [k] __pi___inval_dcache_area 21.66% [mvneta] [k] mvneta_rx_swbm 7.00% [kernel] [k] kmem_cache_alloc 6.05% [kernel] [k] eth_type_trans 4.44% [kernel] [k] kmem_cache_free.part.0 3.80% [kernel] [k] __netif_receive_skb_core 3.68% [kernel] [k] dev_gro_receive 3.65% [kernel] [k] get_page_from_freelist 3.43% [kernel] [k] page_pool_release_page 3.35% [kernel] [k] free_unref_pageAnd this is the same output with recycling enabled:
Overhead Shared Object Symbol 24.10% [kernel] [k] __pi___inval_dcache_area 23.02% [mvneta] [k] mvneta_rx_swbm 7.19% [kernel] [k] kmem_cache_alloc 6.50% [kernel] [k] eth_type_trans 4.93% [kernel] [k] __netif_receive_skb_core 4.77% [kernel] [k] kmem_cache_free.part.0 3.93% [kernel] [k] dev_gro_receive 3.03% [kernel] [k] build_skb 2.91% [kernel] [k] page_pool_put_page 2.85% [kernel] [k] __xdp_return
Quoted 4 lines
The test was done with mausezahn on the TX side with 64 byte raw ethernet frames.
Signed-off-by Matteo Croce <[email protected]>
Other than the typo, I have no objection to the patch.
Quoted 51 lines
--- drivers/net/ethernet/marvell/mvneta.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)drivers/net/ethernet/marvell/mvneta.c +7
-4@@ -2320,7 +2320,7 @@ mvneta_swbm_add_rx_fragment(struct mvneta_port *pp, }static struct sk_buff * -mvneta_swbm_build_skb (struct mvneta_port *pp,struct mvneta_rx_queue *rxq, +mvneta_swbm_build_skb (struct mvneta_port *pp,struct page_pool *pool,struct xdp_buff *xdp,u32 desc_status) {struct skb_shared_info *sinfo =xdp_get_shared_info_from_buff (xdp);@@ -2331,7 +2331,7 @@ mvneta_swbm_build_skb(struct mvneta_port *pp, struct mvneta_rx_queue *rxq,if (!skb)return ERR_PTR (-ENOMEM ); -page_pool_release_page (rxq->page_pool,virt_to_page (xdp->data)); +skb_mark_for_recycle (skb,virt_to_page (xdp->data), pool);skb_reserve (skb, xdp->data - xdp->data_hard_start);skb_put (skb, xdp->data_end - xdp->data);@@ -2343,7 +2343,10 @@ mvneta_swbm_build_skb(struct mvneta_port *pp, struct mvneta_rx_queue *rxq,skb_add_rx_frag (skb,skb_shinfo (skb)->nr_frags,skb_frag_page (frag),skb_frag_off (frag),skb_frag_size (frag),PAGE_SIZE ); -page_pool_release_page (rxq->page_pool,skb_frag_page (frag)); +/* We don't need to reset pp_recycle here. It's already set, so +* just mark fragments for recycling. +*/ +page_pool_store_mem_info (skb_frag_page (frag), pool); }return skb;@@ -2425,7 +2428,7 @@ static int mvneta_rx_swbm(struct napi_struct *napi, mvneta_run_xdp(pp, rxq, xdp_prog, &xdp_buf, frame_sz, &ps)) goto next; - skb =mvneta_swbm_build_skb (pp, rxq, &xdp_buf, desc_status); + skb =mvneta_swbm_build_skb (pp, pp, &xdp_buf, desc_status);if (IS_ERR (skb)) {struct mvneta_pcpu_stats *stats =this_cpu_ptr (pp->stats);Signature · 1 line
2.31.1
Signature · 2 lines
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
Re: [PATCH net-next v5 4/5] mvpp2: recycle buffers
In reply to Russell King (Oracle)Quoted 33 lines · Russell King (Oracle)
Quoted 31 lines · Matteo Croce
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c +8
-0@@ -3847,6 +3847,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,struct mvpp2_pcpu_stats ps = {};enum dma_data_direction dma_dir;struct bpf_prog *xdp_prog; +struct xdp_rxq_info *rxqi;struct xdp_buff xdp;int rx_received;int rx_done =0 ;@@ -3912,15 +3913,15 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi,else frag_size = bm_pool->frag_size; +if (bm_pool->pkt_size ==MVPP2_BM_SHORT_PKT_SIZE ) + rxqi = &rxq->xdp_rxq_short; +else + rxqi = &rxq->xdp_rxq_long; +if (xdp_prog) { + xdp.rxq = rxqi; +xdp_init_buff (&xdp,PAGE_SIZE , rxqi);xdp_prepare_buff (&xdp, data,MVPP2_MH_SIZE +MVPP2_SKB_HEADROOM , rx_bytes, false);@@ -3964,7 +3965,7 @@ static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi, }
Quoted 12 lines
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c static int mvpp2_rx(struct mvpp2_port *port, struct napi_struct *napi, · line 3971
Quoted 5 lines
drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c +1
-0if (pp) +skb_mark_for_recycle (skb,virt_to_page (data), pp);else dma_unmap_single_attrs(dev->dev.parent, dma_addr, bm_pool->buf_size, DMA_FROM_DEVICE,Looking at the above, which I've only quoted the _resulting_ code after your patch above, I don't see why you have moved the "
bm_pool->pkt_size==MVPP2_BM_SHORT_PKT_SIZE" conditional outside of the test forxdp_prog- I don't see rxqi being used except within that conditional. Please can you explain the reasoning there?
Back in v3, skb_mark_for_recycle() was accepting an xdp_mem_info*, so I needed rxqi out of that conditional scope to get that pointer. Now we just need a page_pool*, so I can restore the original chunk. Nice catch.
Thanks,
Signature · 1 line
per aspera ad upstream
Re: [PATCH net-next v5 1/5] mm: add a signature in struct page
In reply to Matteo Croceinclude/linux/mm_types.h struct page { · line 102
Quoted 5 lines · Matteo Croce
include/linux/mm_types.h +4
-0struct {/* page_pool used by netstack */ +/** +* @pp_magic: magic value to avoid recycling non +* page_pool allocated pages. +* It aliases with page->lru.next
I'm not really keen on documenting what aliases with what. pp_magic also aliases with compound_head, 'next' (for slab), and dev_pagemap. This is an O(n^2) documentation problem ...
I feel like I want to document the pfmemalloc bit in mm_types.h, but I don't have a concrete suggestion yet.
include/net/page_pool.h line 66
Quoted 6 lines
+++
b/include/net/page_pool.hinclude/net/page_pool.h +1
-0@@ -63,6 +63,8 @@*/ #define PP_ALLOC_CACHE_SIZE 128#define PP_ALLOC_CACHE_REFILL 64 +#define PP_SIGNATURE (POISON_POINTER_DELTA + 0x40)
I wonder if this wouldn't be better in linux/poison.h?
Re: [PATCH net-next v5 1/5] mm: add a signature in struct page
Quoted 8 lines · Matthew Wilcox
include/linux/mm_types.h struct page { · line 102
Quoted 5 lines · Matteo Croce
struct { /*
page_poolused by netstack */include/linux/mm_types.h +4
-0+/** +* @pp_magic: magic value to avoid recycling non +* page_pool allocated pages. +* It aliases with page->lru.next
Quoted 4 lines
I'm not really keen on documenting what aliases with what.
pp_magicalso aliases withcompound_head, 'next' (for slab), anddev_pagemap. This is an O(n^2) documentation problem ...
Eric asked to document what page->signature aliases, so I did it in the commit message and in a comment.
I can drop the code comment and leave it just the commit message.
Quoted 12 lines
I feel like I want to document the pfmemalloc bit in
mm_types.h, but I don't have a concrete suggestion yet.include/net/page_pool.h line 66
Quoted 6 lines
+++
b/include/net/page_pool.hinclude/net/page_pool.h +1
-0@@ -63,6 +63,8 @@*/ #define PP_ALLOC_CACHE_SIZE 128#define PP_ALLOC_CACHE_REFILL 64 +#define PP_SIGNATURE (POISON_POINTER_DELTA + 0x40)I wonder if this wouldn't be better in
linux/poison.h?
I was thinking the same, I'll do it in the v6.
Regards,
Signature · 1 line
per aspera ad upstream
Re: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
In reply to Matteo CroceQuoted 86 lines · Matteo Croce
From: Ilias Apalodimas <[email protected]>
Up to now several high speed NICs have custom mechanisms of recycling the allocated memory they use for their payloads.
Ourpage_poolAPI already has recycling capabilities that are always used when we are running in 'XDP mode'. So let's tweak the API and the kernel network stack slightly and allow the recycling to happen even during the standard operation.
The API doesn't take into account 'split page' policies used by those drivers currently, but can be extended once we have users for that.The idea is to be able to intercept the packet on
skb_release_data(). If it's a buffer coming from ourpage_poolAPI recycle it back to the pool for further usage or just release the packet entirely.To achieve that we introduce a bit in struct
sk_buff(pp_recycle:1) and a field in struct page (page->pp) to store thepage_poolpointer. Storing the information inpage->ppallows us to recycle both SKBs and their fragments.
The SKB bit is needed for a couple of reasons. First of all in an effort to affect the free path as less as possible, reading a single bit, is better that trying to derive identical information for the page stored data. We do have a special mark in the page, that won't allow this to happen, but again deciding without having to read the entire page is preferable.The driver has to take care of the sync operations on it's own during the buffer recycling since the buffer is, after opting-in to the recycling, never unmapped.
Since the gain on the drivers depends on the architecture, we are not enabling recycling by default if the
page_poolAPI is used on a driver. In order to enable recycling the driver must callskb_mark_for_recycle()to store the information we need for recycling inpage->ppand enabling the recycling bit, orpage_pool_store_mem_info()for a fragment.Co-developed-by Jesper Dangaard Brouer <[email protected]>Signed-off-by Jesper Dangaard Brouer <[email protected]>Co-developed-by Matteo Croce <[email protected]>Signed-off-by Matteo Croce <[email protected]>Signed-off-by Ilias Apalodimas <[email protected]>--- include/linux/skbuff.h | 28 +++++++++++++++++++++++++--- include/net/page_pool.h | 9 +++++++++ net/core/page_pool.c | 23 +++++++++++++++++++++++ net/core/skbuff.c | 25 +++++++++++++++++++++---- 4 files changed, 78 insertions(+), 7 deletions(-)include/linux/skbuff.h +8
-1@@ -40,6 +40,9 @@#if IS_ENABLED (CONFIG_NF_CONNTRACK )#include <linux/netfilter/nf_conntrack_common.h> #endif +#ifdef CONFIG_PAGE_POOL +#include <net/page_pool.h> +#endif /* The interface for checksum offload between the stack and networking drivers * is as follows... @@ -667,6 +670,8 @@ typedef unsigned char *sk_buff_data_t;* @head_frag: skb was allocated from page fragments, * not allocated by kmalloc() or vmalloc(). * @pfmemalloc: skbuff was allocated from PFMEMALLOC reserves +* @pp_recycle: mark the packet for recycling instead of freeing (implies +* page_pool support on driver) * @active_extensions: active extensions (skb_ext_id types) * @ndisc_nodetype: router type (from link layer) * @ooo_okay: allow the mapping of a socket to a queue to be changed @@ -791,10 +796,12 @@ struct sk_buff { fclone:2, peeked:1, head_frag:1, - pfmemalloc:1; + pfmemalloc:1, + pp_recycle:1; /* page_pool recycle indicator */#ifdef CONFIG_SKB_EXTENSIONS __u8 active_extensions;#endif +/* fields enclosed in headers_start/headers_end are copied * using a single memcpy() in __copy_skb_header() */
include/linux/skbuff.h static inline void skb_frag_ref(struct sk_buff *skb, int f) · line 3096
Quoted 2 lines
include/linux/skbuff.h +0
-0@@ -3088,7 +3095,13 @@ static inline void skb_frag_ref(struct sk_buff *skb, int f)*/ static inline void __skb_frag_unref (skb_frag_t *frag,bool recycle)
Does it make sure to define a new function like recyclable_skb_frag_unref() instead of adding the recycle parameter? This way we may avoid checking skb->pp_recycle for head data and every frag?
Quoted 67 lines
include/linux/skbuff.h +17
-2{ -put_page (skb_frag_page (frag)); +struct page *page =skb_frag_page (frag); + +#ifdef CONFIG_PAGE_POOL +if (recycle &&page_pool_return_skb_page (page_address (page))) +return ; +#endif +put_page (page); }/** @@ -3100,7 +3113,7 @@ static inline void __skb_frag_unref(skb_frag_t *frag, bool recycle)*/ static inline void skb_frag_unref (struct sk_buff *skb,int f) { -__skb_frag_unref (&skb_shinfo (skb)->frags[f], false); +__skb_frag_unref (&skb_shinfo (skb)->frags[f], skb->pp_recycle); }/** @@ -4699,5 +4712,14 @@ static inline u64 skb_get_kcov_handle(struct sk_buff *skb)#endif } +#ifdef CONFIG_PAGE_POOL +static inline void skb_mark_for_recycle (struct sk_buff *skb,struct page *page, +struct page_pool *pp) +{ + skb->pp_recycle =1 ; +page_pool_store_mem_info (page, pp); +} +#endif +#endif /* __KERNEL__ */ #endif /* _LINUX_SKBUFF_H */ include/net/page_pool.h +9
-0@@ -148,6 +148,8 @@ inline enum dma_data_direction page_pool_get_dma_dir(struct page_pool *pool)return pool->p.dma_dir; } +bool page_pool_return_skb_page (void *data); +struct page_pool *page_pool_create (const struct page_pool_params *params);#ifdef CONFIG_PAGE_POOL @@ -253,4 +255,11 @@ static inline void page_pool_ring_unlock(struct page_pool *pool) spin_unlock_bh(&pool->ring.producer_lock); } +/* Store mem_info on struct page and use it while recycling skb frags */ +static inline +void page_pool_store_mem_info (struct page *page,struct page_pool *pp) +{ + page->pp = pp; +} +#endif /* _NET_PAGE_POOL_H */ net/core/page_pool.c +0
-0@@ -626,3 +626,26 @@ void page_pool_update_nid(struct page_pool *pool, int new_nid) }
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 636
Quoted 10 lines
net/core/page_pool.c +8
-0}EXPORT_SYMBOL (page_pool_update_nid); + +bool page_pool_return_skb_page (void *data) +{ +struct page_pool *pp; +struct page *page; + + page =virt_to_head_page (data); +if (unlikely (page->pp_magic !=PP_SIGNATURE ))
we have checked the skb->pp_recycle before checking the page->pp_magic, so the above seems like a likely() instead of unlikely()?
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 646
Quoted 10 lines
net/core/page_pool.c +10
-0+return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model. +* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ;
Why not only clear the page->pp when the page can not be recycled by the page pool? so that we do not need to set and clear it every time the page is recycled。
Quoted 55 lines
net/core/page_pool.c +5
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); + +return true; +} +EXPORT_SYMBOL (page_pool_return_skb_page);net/core/skbuff.c +12
-3@@ -70,6 +70,9 @@#include <net/xfrm.h> #include <net/mpls.h> #include <net/mptcp.h> +#ifdef CONFIG_PAGE_POOL +#include <net/page_pool.h> +#endif #include <linux/uaccess.h> #include <trace/events/skb.h> @@ -645,10 +648,15 @@ static void skb_free_head(struct sk_buff *skb) {unsigned char *head = skb->head; -if (skb->head_frag) +if (skb->head_frag) { +#ifdef CONFIG_PAGE_POOL +if (skb->pp_recycle &&page_pool_return_skb_page (head)) +return ; +#endif skb_free_frag (head); -else + }else {kfree (head); + } }static void skb_release_data (struct sk_buff *skb)@@ -664,7 +672,7 @@ static void skb_release_data(struct sk_buff *skb)skb_zcopy_clear (skb, true);for (i =0 ; i < shinfo->nr_frags; i++) -__skb_frag_unref (&shinfo->frags[i], false); +__skb_frag_unref (&shinfo->frags[i], skb->pp_recycle);if (shinfo->frag_list)kfree_skb_list (shinfo->frag_list);@@ -1046,6 +1054,7 @@ static struct sk_buff *__skb_clone(struct sk_buff *n, struct sk_buff *skb) n->nohdr =0 ; n->peeked =0 ;C (pfmemalloc); +C (pp_recycle); n->destructor =NULL ;C (tail);C (end);
net/core/skbuff.c int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail, · line 1737
Quoted 4 lines
net/core/skbuff.c +1
-0@@ -1725,6 +1734,7 @@ int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail, skb->cloned =0 ; skb->hdr_len =0 ; skb->nohdr =0 ; + skb->pp_recycle =0 ;
I am not sure why we clear the skb->pp_recycle here.
As my understanding, the pskb_expand_head() only allocate new head data, the old frag page in skb_shinfo()->frags still could be from page pool, right?
Quoted 13 lines
net/core/skbuff.c +1
-1atomic_set (&skb_shinfo (skb)->dataref,1 );skb_metadata_clear (skb);@@ -3495,7 +3505,7 @@ int skb_shift(struct sk_buff *tgt, struct sk_buff *skb, int shiftlen) fragto = &skb_shinfo (tgt)->frags[merge];skb_frag_size_add (fragto,skb_frag_size (fragfrom)); -__skb_frag_unref (fragfrom, false); +__skb_frag_unref (fragfrom, skb->pp_recycle); }/* Reposition in the original skb */
net/core/skbuff.c bool skb_try_coalesce(struct sk_buff *to, struct sk_buff *from, · line 5303
Quoted 9 lines
net/core/skbuff.c +6
-0@@ -5285,6 +5295,13 @@ bool skb_try_coalesce(struct sk_buff *to, struct sk_buff *from,if (skb_cloned (to))return false; +/* We can't coalesce skb that are allocated from slab and page_pool +* The recycle mark is on the skb, so that might end up trying to +* recycle slab allocated skb->head +*/ +if (to->pp_recycle != from->pp_recycle) +return false;
Since we are also depending on page->pp_magic to decide whether to recycle a page, we could just set the to->pp_recycle according to from->pp_recycle and do the coalesce?
Quoted 5 lines
net/core/skbuff.c +1
-0+if (len <=skb_tailroom (to)) {if (len)BUG_ON (skb_copy_bits (from,0 ,skb_put (to, len), len));
Ilias Apalodimas
maintainerRe: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
[...]
Quoted 10 lines
include/linux/skbuff.h static inline void skb_frag_ref(struct sk_buff *skb, int f) · line 3096
Quoted 5 lines
include/linux/skbuff.h +0
-0* using a single memcpy() in __copy_skb_header() */ @@ -3088,7 +3095,13 @@ static inline void skb_frag_ref(struct sk_buff *skb, int f)*/ static inline void __skb_frag_unref (skb_frag_t *frag,bool recycle)Does it make sure to define a new function like
recyclable_skb_frag_unref()instead of adding the recycle parameter? This way we may avoid checkingskb->pp_recyclefor head data and every frag?
We'd still have to check when to run __skb_frag_unref or recyclable_skb_frag_unref so I am not sure we can avoid that. In any case I'll have a look
Quoted 72 lines
Quoted 72 lines
include/linux/skbuff.h +17
-2{ -put_page (skb_frag_page (frag)); +struct page *page =skb_frag_page (frag); + +#ifdef CONFIG_PAGE_POOL +if (recycle &&page_pool_return_skb_page (page_address (page))) +return ; +#endif +put_page (page); }/** @@ -3100,7 +3113,7 @@ static inline void __skb_frag_unref(skb_frag_t *frag, bool recycle)*/ static inline void skb_frag_unref (struct sk_buff *skb,int f) { -__skb_frag_unref (&skb_shinfo (skb)->frags[f], false); +__skb_frag_unref (&skb_shinfo (skb)->frags[f], skb->pp_recycle); }/** @@ -4699,5 +4712,14 @@ static inline u64 skb_get_kcov_handle(struct sk_buff *skb)#endif } +#ifdef CONFIG_PAGE_POOL +static inline void skb_mark_for_recycle (struct sk_buff *skb,struct page *page, +struct page_pool *pp) +{ + skb->pp_recycle =1 ; +page_pool_store_mem_info (page, pp); +} +#endif +#endif /* __KERNEL__ */ #endif /* _LINUX_SKBUFF_H */ include/net/page_pool.h +9
-0@@ -148,6 +148,8 @@ inline enum dma_data_direction page_pool_get_dma_dir(struct page_pool *pool)return pool->p.dma_dir; } +bool page_pool_return_skb_page (void *data); +struct page_pool *page_pool_create (const struct page_pool_params *params);#ifdef CONFIG_PAGE_POOL @@ -253,4 +255,11 @@ static inline void page_pool_ring_unlock(struct page_pool *pool) spin_unlock_bh(&pool->ring.producer_lock); } +/* Store mem_info on struct page and use it while recycling skb frags */ +static inline +void page_pool_store_mem_info (struct page *page,struct page_pool *pp) +{ + page->pp = pp; +} +#endif /* _NET_PAGE_POOL_H */ net/core/page_pool.c +3
-0@@ -626,3 +626,26 @@ void page_pool_update_nid(struct page_pool *pool, int new_nid) } }EXPORT_SYMBOL (page_pool_update_nid); + +bool page_pool_return_skb_page (void *data) +{
Quoted 9 lines
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 636
Quoted 5 lines
net/core/page_pool.c +5
-0+struct page_pool *pp; +struct page *page; + + page =virt_to_head_page (data); +if (unlikely (page->pp_magic !=PP_SIGNATURE ))we have checked the
skb->pp_recyclebefore checking thepage->pp_magic, so the above seems like alikely()instead ofunlikely()?
The check here is ! = PP_SIGNATURE. So since we already checked for pp_recycle, it's unlikely the signature won't match.
Quoted 6 lines
Quoted 6 lines
net/core/page_pool.c +6
-0+return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model.
Quoted 9 lines
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 646
Quoted 4 lines
net/core/page_pool.c +4
-0+* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ;Why not only clear the
page->ppwhen the page can not be recycled by the page pool? so that we do not need to set and clear it every time the page is recycled。
If the page cannot be recycled, page->pp will not probably be set to begin with. Since we don't embed the feature in page_pool and we require the driver to explicitly enable it, as part of the 'skb flow', I'd rather keep it as is. When we set/clear the page->pp, the page is probably already in cache, so I doubt this will have any measurable impact.
Quoted 3 lines
Quoted 3 lines
net/core/page_pool.c +2
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); +C (end);
[...]
Quoted 11 lines
net/core/page_pool.c int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail, · line 1737
Quoted 5 lines
net/core/page_pool.c +1
-0@@ -1725,6 +1734,7 @@ int pskb_expand_head(struct sk_buff *skb, int nhead, int ntail, skb->cloned =0 ; skb->hdr_len =0 ; skb->nohdr =0 ; + skb->pp_recycle =0 ;I am not sure why we clear the
skb->pp_recyclehere.
As my understanding, thepskb_expand_head()only allocate new head data, the old frag page in skb_shinfo()->frags still could be from page pool, right?
Ah correct! In that case we must not clear skb->pp_recycle. The new head will fail on the signature check and end up being freed, while the remaining frags will be recycled. The *original* head will be unmapped/recycled (based of the page refcnt) on the pskb_expand_head() itself.
Quoted 16 lines
Quoted 16 lines
net/core/page_pool.c +1
-1atomic_set (&skb_shinfo (skb)->dataref,1 );skb_metadata_clear (skb);@@ -3495,7 +3505,7 @@ int skb_shift(struct sk_buff *tgt, struct sk_buff *skb, int shiftlen) fragto = &skb_shinfo (tgt)->frags[merge];skb_frag_size_add (fragto,skb_frag_size (fragfrom)); -__skb_frag_unref (fragfrom, false); +__skb_frag_unref (fragfrom, skb->pp_recycle); }/* Reposition in the original skb */ @@ -5285,6 +5295,13 @@ bool skb_try_coalesce(struct sk_buff *to, struct sk_buff *from,if (skb_cloned (to))return false;
Quoted 10 lines
net/core/page_pool.c bool skb_try_coalesce(struct sk_buff *to, struct sk_buff *from, · line 5303
Quoted 6 lines
net/core/page_pool.c +6
-0+/* We can't coalesce skb that are allocated from slab and page_pool +* The recycle mark is on the skb, so that might end up trying to +* recycle slab allocated skb->head +*/ +if (to->pp_recycle != from->pp_recycle) +return false;Since we are also depending on
page->pp_magicto decide whether to recycle a page, we could just set theto->pp_recycleaccording tofrom->pp_recycleand do the coalesce?
So I was think about this myself. This check is a 'leftover' from my initial version, were I only had the pp_recycle bit + struct page meta-data (without the signature). Since that version didn't have the signature you could not coalesce 2 skb's coming from page_pool/slab. We could now do what you suggest, but honestly I can't think of many use cases that this can happen to begin with. I think I'd prefer leaving it as is and adjusting the comment. If we can somehow prove this happens oftenly and has a performance impact, we can go ahead and remove it.
[...]
Thanks
/Ilias
Re: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 17 lines · Ilias Apalodimas
[...]
Quoted 6 lines
Quoted 6 lines
net/core/page_pool.c +6
-0+return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model. Quoted 9 lines
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 646
Quoted 4 lines
net/core/page_pool.c +4
-0+* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ;Why not only clear the
page->ppwhen the page can not be recycled by the page pool? so that we do not need to set and clear it every time the page is recycled。
Quoted 5 lines
If the page cannot be recycled,
page->ppwill not probably be set to begin with. Since we don't embed the feature inpage_pooland we require the driver to explicitly enable it, as part of the 'skb flow', I'd rather keep it as is. When we set/clear thepage->pp, the page is probably already in cache, so I doubt this will have any measurable impact.
The point is that we already have the skb->pp_recycle to let driver to explicitly enable recycling, as part of the 'skb flow, if the page pool keep the page->pp while it owns the page, then the driver may only need to call one skb_mark_for_recycle() for a skb, instead of call skb_mark_for_recycle() for each page frag of a skb.
Maybe we can add a parameter in "struct page_pool_params" to let driver to decide if the page pool ptr is stored in page->pp while the page pool owns the page?
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems the skb_mark_for_recycle() call does not seems to add any value?
Quoted 6 lines
Quoted 4 lines
Quoted 4 lines
net/core/page_pool.c +2
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); +C (end);[...]
Ilias Apalodimas
maintainerRe: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 24 lines · Yunsheng Lin
Quoted 17 lines · Ilias Apalodimas
[...]
Quoted 6 lines
Quoted 6 lines
net/core/page_pool.c +6
-0+return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model. Quoted 9 lines
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 646
Quoted 4 lines
net/core/page_pool.c +4
-0+* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ;Why not only clear the
page->ppwhen the page can not be recycled by the page pool? so that we do not need to set and clear it every time the page is recycled。Quoted 5 lines
If the page cannot be recycled,
page->ppwill not probably be set to begin with. Since we don't embed the feature inpage_pooland we require the driver to explicitly enable it, as part of the 'skb flow', I'd rather keep it as is. When we set/clear thepage->pp, the page is probably already in cache, so I doubt this will have any measurable impact.
Quoted 6 lines
The point is that we already have the
skb->pp_recycleto let driver to explicitly enable recycling, as part of the 'skb flow, if the page pool keep thepage->ppwhile it owns the page, then the driver may only need to call oneskb_mark_for_recycle()for a skb, instead of callskb_mark_for_recycle()for each page frag of a skb.
The driver is meant to call skb_mark_for_recycle for the skb and page_pool_store_mem_info() for the fragments (in order to store page->pp). Nothing bad will happen if you call skb_mark_for_recycle on a frag though, but in any case you need to store the page_pool pointer of each frag to struct page.
Quoted 3 lines
Maybe we can add a parameter in "struct
page_pool_params" to let driver to decide if the page pool ptr is stored inpage->ppwhile the page pool owns the page?
Then you'd have to check the page pool config before saving the meta-data, and you would have to make the skb path aware of that as well (I assume you mean replace pp_recycle with this?).
If not and you just want to add an extra flag on page_pool_params and be able to enable recycling depending on that flag, we just add a patch afterwards. I am not sure we need an extra if for each packet though.
Quoted 6 lines
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call
skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems theskb_mark_for_recycle()call does not seems to add any value?
Not really, the driver has 2 choices:
- call page_pool_release_page() once it receives the payload. That will clean up dma mappings (if page pool is responsible for them) and free the buffer
- call skb_mark_for_recycle(). Which will end up recycling the buffer.
If you call none of those, you'd leak a page, but that's a driver bug. patches [4/5, 5/5] do that for two marvell drivers.
I really want to make drivers opt-in in the feature instead of always enabling it.
Thanks
/Ilias
Quoted 9 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
net/core/page_pool.c +2
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); +C (end);[...]
Re: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 32 lines · Ilias Apalodimas
Quoted 24 lines · Yunsheng Lin
Quoted 17 lines · Ilias Apalodimas
[...]
Quoted 6 lines
Quoted 6 lines
net/core/page_pool.c +6
-0+return false; + + pp = (struct page_pool *)page->pp; + +/* Driver set this to memory recycling info. Reset it on recycle. +* This will *not* work for NIC using a split-page memory model. Quoted 9 lines
net/core/page_pool.c void page_pool_update_nid(struct page_pool *pool, int new_nid) · line 646
Quoted 4 lines
net/core/page_pool.c +4
-0+* The page will be returned to the pool here regardless of the +* 'flipped' fragment being in use or not. +*/ + page->pp =NULL ;Why not only clear the
page->ppwhen the page can not be recycled by the page pool? so that we do not need to set and clear it every time the page is recycled。Quoted 5 lines
If the page cannot be recycled,
page->ppwill not probably be set to begin with. Since we don't embed the feature inpage_pooland we require the driver to explicitly enable it, as part of the 'skb flow', I'd rather keep it as is. When we set/clear thepage->pp, the page is probably already in cache, so I doubt this will have any measurable impact.Quoted 6 lines
The point is that we already have the
skb->pp_recycleto let driver to explicitly enable recycling, as part of the 'skb flow, if the page pool keep thepage->ppwhile it owns the page, then the driver may only need to call oneskb_mark_for_recycle()for a skb, instead of callskb_mark_for_recycle()for each page frag of a skb.
Quoted 5 lines
The driver is meant to call
skb_mark_for_recyclefor the skb andpage_pool_store_mem_info()for the fragments (in order to storepage->pp). Nothing bad will happen if you callskb_mark_for_recycleon a frag though, but in any case you need to store thepage_poolpointer of each frag to struct page.
Right. Nothing bad will happen when we keep the page_pool pointer in page->pp while page pool owns the page too, even if the skb->pp_recycle is not set, right?
Quoted 6 lines
Quoted 4 lines
Maybe we can add a parameter in "struct
page_pool_params" to let driver to decide if the page pool ptr is stored inpage->ppwhile the page pool owns the page?Then you'd have to check the page pool config before saving the meta-data,
I am not sure what the "saving the meta-data" meant?
Quoted 2 lines
and you would have to make the skb path aware of that as well (I assume you mean replace
pp_recyclewith this?).
I meant we could set the in page->pp when the page is allocated from alloc_pages() in __page_pool_alloc_pages_slow() unconditionally or according to a newly add filed in pool->p, and only clear it in page_pool_release_page(), between which the page is owned by page pool, right?
Quoted 3 lines
If not and you just want to add an extra flag on
page_pool_paramsand be able to enable recycling depending on that flag, we just add a patch afterwards. I am not sure we need an extra if for each packet though.
In that case, the skb_mark_for_recycle() could only set the skb->pp_recycle, but not the pool->p.
Quoted 8 lines
Quoted 7 lines
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call
skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems theskb_mark_for_recycle()call does not seems to add any value?
Quoted 4 lines
Not really, the driver has 2 choices:
- callpage_pool_release_page()once it receives the payload. That will clean up dma mappings (if page pool is responsible for them) and free the buffer
The is only needed before SKB recycling is supported or the driver does not want the SKB recycling support explicitly, right?
Quoted 1 line
- call
skb_mark_for_recycle(). Which will end up recycling the buffer.
If the driver need to add extra flag to enable recycling based on skb instead of page pool, then adding skb_mark_for_recycle() makes sense to me too, otherwise it seems adding a field in pool->p to recycling based on skb makes more sense?
Quoted 20 lines
If you call none of those, you'd leak a page, but that's a driver bug. patches [4/5, 5/5] do that for two marvell drivers.
I really want to make drivers opt-in in the feature instead of always enabling it.Thanks
/IliasQuoted 9 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
net/core/page_pool.c +2
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); +C (end);[...]
.
Ilias Apalodimas
maintainerRe: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
[...]
Quoted 23 lines
Quoted 17 lines
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines
by the page pool? so that we do not need to set and clear it every time the page is recycled。
If the page cannot be recycled,
page->ppwill not probably be set to begin with. Since we don't embed the feature inpage_pooland we require the driver to explicitly enable it, as part of the 'skb flow', I'd rather keep it as is. When we set/clear thepage->pp, the page is probably already in cache, so I doubt this will have any measurable impact.Quoted 6 lines
The point is that we already have the
skb->pp_recycleto let driver to explicitly enable recycling, as part of the 'skb flow, if the page pool keep thepage->ppwhile it owns the page, then the driver may only need to call oneskb_mark_for_recycle()for a skb, instead of callskb_mark_for_recycle()for each page frag of a skb.Quoted 5 lines
The driver is meant to call
skb_mark_for_recyclefor the skb andpage_pool_store_mem_info()for the fragments (in order to storepage->pp). Nothing bad will happen if you callskb_mark_for_recycleon a frag though, but in any case you need to store thepage_poolpointer of each frag to struct page.
Quoted 3 lines
Right. Nothing bad will happen when we keep the
page_poolpointer inpage->ppwhile page pool owns the page too, even if theskb->pp_recycleis not set, right?
Yep, nothing bad will happen. Both functions using this (__skb_frag_unref and skb_free_head) always check the skb bit as well.
Quoted 9 lines
Quoted 7 lines
Quoted 5 lines
Maybe we can add a parameter in "struct
page_pool_params" to let driver to decide if the page pool ptr is stored inpage->ppwhile the page pool owns the page?Then you'd have to check the page pool config before saving the meta-data,
I am not sure what the "saving the meta-data" meant?
I was referring to struct page_pool* and the signature we store in struct page.
Quoted 25 lines
Quoted 3 lines
and you would have to make the skb path aware of that as well (I assume you mean replace
pp_recyclewith this?).I meant we could set the in
page->ppwhen the page is allocated fromalloc_pages()in__page_pool_alloc_pages_slow()unconditionally or according to a newly add filed inpool->p, and only clear it inpage_pool_release_page(), between which the page is owned by page pool, right?Quoted 3 lines
If not and you just want to add an extra flag on
page_pool_paramsand be able to enable recycling depending on that flag, we just add a patch afterwards. I am not sure we need an extra if for each packet though.In that case, the
skb_mark_for_recycle()could only set theskb->pp_recycle, but not thepool->p.Quoted 8 lines
Quoted 7 lines
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call
skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems theskb_mark_for_recycle()call does not seems to add any value?
Quoted 8 lines
Quoted 4 lines
Not really, the driver has 2 choices:
- callpage_pool_release_page()once it receives the payload. That will clean up dma mappings (if page pool is responsible for them) and free the bufferThe is only needed before SKB recycling is supported or the driver does not want the SKB recycling support explicitly, right?
This is needed in general even before recycling. It's used to unmap the buffer, so once you free the SKB you don't leave any stale DMA mappings. So that's what all the drivers that use page_pool call today.
Quoted 7 lines
Quoted 1 line
- call
skb_mark_for_recycle(). Which will end up recycling the buffer.If the driver need to add extra flag to enable recycling based on skb instead of page pool, then adding
skb_mark_for_recycle()makes sense to me too, otherwise it seems adding a field inpool->pto recycling based on skb makes more sense?
The recycling is essentially an SKB feature though isn't it? You achieve the SKB recycling with the help of page_pool API, not the other way around. So I think this should remain on the SKB and maybe in the future find ways to turn in on/off?
Thanks
/Ilias
Quoted 21 lines
Quoted 20 lines
If you call none of those, you'd leak a page, but that's a driver bug. patches [4/5, 5/5] do that for two marvell drivers.
I really want to make drivers opt-in in the feature instead of always enabling it.Thanks
/IliasQuoted 9 lines
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
net/core/page_pool.c +2
-0+page_pool_put_full_page (pp,virt_to_head_page (data), false); +C (end);[...]
.
Re: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 44 lines · Ilias Apalodimas
[...]
Quoted 9 lines
Quoted 7 lines
Quoted 5 lines
Maybe we can add a parameter in "struct
page_pool_params" to let driver to decide if the page pool ptr is stored inpage->ppwhile the page pool owns the page?Then you'd have to check the page pool config before saving the meta-data,
I am not sure what the "saving the meta-data" meant?
I was referring to struct page_pool* and the signature we store in struct page.
Quoted 30 lines
Quoted 3 lines
and you would have to make the skb path aware of that as well (I assume you mean replace
pp_recyclewith this?).I meant we could set the in
page->ppwhen the page is allocated fromalloc_pages()in__page_pool_alloc_pages_slow()unconditionally or according to a newly add filed inpool->p, and only clear it inpage_pool_release_page(), between which the page is owned by page pool, right?Quoted 3 lines
If not and you just want to add an extra flag on
page_pool_paramsand be able to enable recycling depending on that flag, we just add a patch afterwards. I am not sure we need an extra if for each packet though.In that case, the
skb_mark_for_recycle()could only set theskb->pp_recycle, but not thepool->p.Quoted 12 lines
Quoted 7 lines
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call
skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems theskb_mark_for_recycle()call does not seems to add any value?Not really, the driver has 2 choices:
- callpage_pool_release_page()once it receives the payload. That will clean up dma mappings (if page pool is responsible for them) and free the buffer
Quoted 7 lines
Quoted 3 lines
The is only needed before SKB recycling is supported or the driver does not want the SKB recycling support explicitly, right?
This is needed in general even before recycling. It's used to unmap the buffer, so once you free the SKB you don't leave any stale DMA mappings. So that's what all the drivers that use
page_poolcall today.
As my understanding:
1. If the driver is using page allocated from page allocator directly to form a skb, let's say the page is owned by skb(or not owned by anyone:)), when a skb is freed, the put_page() should be called.
2. If the driver is using page allocated from page pool to form a skb, let's say the page is owned by page pool, when a skb is freed, page_pool_put_page() should be called.
What page_pool_release_page() mainly do is to make page in case 2 return back to case 1.
And page_pool_release_page() is replaced with skb_mark_for_recycle() in patch 4/5 to avoid the above "case 2" -> "case 1" changing, so that the page is still owned by page pool, right?
So the point is that skb_mark_for_recycle() does not really do anything about the owner of the page, it is still owned by page pool, so it makes more sense to keep the page pool ptr instead of setting it every time when skb_mark_for_recycle() is called?
Quoted 9 lines
Quoted 8 lines
Quoted 2 lines
- call
skb_mark_for_recycle(). Which will end up recycling the buffer.If the driver need to add extra flag to enable recycling based on skb instead of page pool, then adding
skb_mark_for_recycle()makes sense to me too, otherwise it seems adding a field inpool->pto recycling based on skb makes more sense?
Quoted 4 lines
The recycling is essentially an SKB feature though isn't it? You achieve the SKB recycling with the help of
page_poolAPI, not the other way around. So I think this should remain on the SKB and maybe in the future find ways to turn in on/off?
As above, does it not make more sense to call page_pool_release_page() if the driver does not need the SKB recycling?
Even if when skb->pp_recycle is 1, pages allocated from page allocator directly or page pool are both supported, so it seems page->signature need to be reliable to indicate a page is indeed owned by a page pool, which means the skb->pp_recycle is used mainly to short cut the code path for skb->pp_recycle is 0 case, so that the page->signature does not need checking?
Quoted 3 lines
Thanks
/Ilias
Ilias Apalodimas
maintainerRe: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 1 line
Quoted 1 line
Quoted 1 line
[...]
Quoted 29 lines
Quoted 16 lines
Quoted 16 lines
In that case, the
skb_mark_for_recycle()could only set theskb->pp_recycle, but not thepool->p.Quoted 12 lines
Quoted 7 lines
Another thing accured to me is that if the driver use page from the page pool to form a skb, and it does not call
skb_mark_for_recycle(), then there will be resource leaking, right? if yes, it seems theskb_mark_for_recycle()call does not seems to add any value?Not really, the driver has 2 choices:
- callpage_pool_release_page()once it receives the payload. That will clean up dma mappings (if page pool is responsible for them) and free the bufferQuoted 7 lines
Quoted 3 lines
The is only needed before SKB recycling is supported or the driver does not want the SKB recycling support explicitly, right?
This is needed in general even before recycling. It's used to unmap the buffer, so once you free the SKB you don't leave any stale DMA mappings. So that's what all the drivers that use
page_poolcall today.As my understanding:
1. If the driver is using page allocated from page allocator directly to form a skb, let's say the page is owned by skb(or not owned by anyone:)), when a skb is freed, theput_page()should be called.
Quoted 6 lines
2. If the driver is using page allocated from page pool to form a skb, let's say the page is owned by page pool, when a skb is freed,
page_pool_put_page()should be called.What
page_pool_release_page()mainly do is to make page in case 2 return back to case 1.
Yea but this is done deliberately. Let me try to explain the reasoning a bit. I don't think mixing the SKB path with page_pool is the right idea. page_pool allocates the memory you want to build an SKB and imho it must be kept completely disjoint with the generic SKB code. So once you free an SKB, I don't like having page_pool_put_page() in the release code explicitly. What we do instead is call page_pool_release_page() from the driver. So the page is disconnected from page pool and the skb release path works as it used to.
Quoted 9 lines
And
page_pool_release_page()is replaced withskb_mark_for_recycle()in patch 4/5 to avoid the above "case 2" -> "case 1" changing, so that the page is still owned by page pool, right?So the point is that
skb_mark_for_recycle()does not really do anything about the owner of the page, it is still owned by page pool, so it makes more sense to keep the page pool ptr instead of setting it every time whenskb_mark_for_recycle()is called?
Yes it doesn't do anything wrt to ownership. The page must always come from page pool if you want to recycle it. But as I tried to explain above, it felt more intuitive to keep the driver flow as-is as well as the release path. On a driver right now when you are done with the skb creation, you unmap the skb->head + fragments. So if you want to recycle it it instead, you mark the skb and fragments.
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Quoted 3 lines
- call
skb_mark_for_recycle(). Which will end up recycling the buffer.If the driver need to add extra flag to enable recycling based on skb instead of page pool, then adding
skb_mark_for_recycle()makes sense to me too, otherwise it seems adding a field inpool->pto recycling based on skb makes more sense?
Quoted 7 lines
Quoted 4 lines
The recycling is essentially an SKB feature though isn't it? You achieve the SKB recycling with the help of
page_poolAPI, not the other way around. So I think this should remain on the SKB and maybe in the future find ways to turn in on/off?As above, does it not make more sense to call
page_pool_release_page()if the driver does not need the SKB recycling?
Call it were? As i tried to explain it makes no sense to me having it in generic SKB code (unless recycling is enabled).
That's what's happening right now when recycling is enabled. Basically the call path is:
if (skb bit is set) {
if (page signature matches)
page_pool_put_full_page()
}page_pool_put_full_page() will either:
1. recycle the page in the 'fast cache' of page pool
2. recycle the page in the ptr ring of page pool
3. Release it calling page_pool_release_page()
If you don't want to enable it you just call page_pool_release_page() on your driver and the generic path will free the allocated page.
Quoted 6 lines
Even if when
skb->pp_recycleis 1, pages allocated from page allocator directly or page pool are both supported, so it seemspage->signatureneed to be reliable to indicate a page is indeed owned by a page pool, which means theskb->pp_recycleis used mainly to short cut the code path forskb->pp_recycleis 0 case, so that thepage->signaturedoes not need checking?
Yes, the idea for the recycling bit, is that you don't have to fetch the page in cache do do more processing (since freeing is asynchronous and we can't have any guarantees on what the cache will have at that point). So we are trying to affect the existing release path a less as possible. However it's that new skb bit that triggers the whole path.
What you propose could still be doable though. As you said we can add the page pointer to struct page when we allocate a page_pool page and never reset it when we recycle the buffer. But I don't think there will be any performance impact whatsoever. So I prefer the 'visible' approach, at least for the first iteration.
Thanks
/Ilias
Re: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 13 lines · Ilias Apalodimas
Quoted 6 lines
Even if when
skb->pp_recycleis 1, pages allocated from page allocator directly or page pool are both supported, so it seemspage->signatureneed to be reliable to indicate a page is indeed owned by a page pool, which means theskb->pp_recycleis used mainly to short cut the code path forskb->pp_recycleis 0 case, so that thepage->signaturedoes not need checking?Yes, the idea for the recycling bit, is that you don't have to fetch the page in cache do do more processing (since freeing is asynchronous and we can't have any guarantees on what the cache will have at that point). So we are trying to affect the existing release path a less as possible. However it's that new skb bit that triggers the whole path.
Quoted 4 lines
What you propose could still be doable though. As you said we can add the page pointer to struct page when we allocate a
page_poolpage and never reset it when we recycle the buffer. But I don't think there will be any performance impact whatsoever. So I prefer the 'visible' approach, at least for
setting and unsetting the page_pool ptr every time the page is recycled may cause a cache bouncing problem when rx cleaning and skb releasing is not happening on the same cpu.
Quoted 8 lines
the first iteration.
Thanks
/Ilias.
Ilias Apalodimas
maintainerRe: [PATCH net-next v5 3/5] page_pool: Allow drivers to hint on SKB recycling
Quoted 14 lines · Yunsheng Lin
Quoted 13 lines · Ilias Apalodimas
Quoted 6 lines
Even if when
skb->pp_recycleis 1, pages allocated from page allocator directly or page pool are both supported, so it seemspage->signatureneed to be reliable to indicate a page is indeed owned by a page pool, which means theskb->pp_recycleis used mainly to short cut the code path forskb->pp_recycleis 0 case, so that thepage->signaturedoes not need checking?Yes, the idea for the recycling bit, is that you don't have to fetch the page in cache do do more processing (since freeing is asynchronous and we can't have any guarantees on what the cache will have at that point). So we are trying to affect the existing release path a less as possible. However it's that new skb bit that triggers the whole path.
Quoted 8 lines
Quoted 4 lines
What you propose could still be doable though. As you said we can add the page pointer to struct page when we allocate a
page_poolpage and never reset it when we recycle the buffer. But I don't think there will be any performance impact whatsoever. So I prefer the 'visible' approach, at least forsetting and unsetting the
page_poolptr every time the page is recycled may cause a cache bouncing problem when rx cleaning and skb releasing is not happening on the same cpu.
In our case since the skb is asynchronous and not protected by a NAPI context, the buffer wont end up in the 'fast' page pool cache. So we'll recycle by calling page_pool_recycle_in_ring() not page_pool_recycle_in_cache(). Which means that the page you recycled will be re-filled later, in batches, when page_pool_refill_alloc_cache() is called to refill the fast cache. I am not i saying it might not happen, but I don't really know if it's going to make a difference or not. So I just really prefer taking this as is and perhaps later, when 40/100gbit drivers start using it we can justify the optimization (along with supporting the split page model).
Thanks
/Ilias
Quoted 10 lines
Quoted 9 lines
the first iteration.
Thanks
/Ilias.
Re: [PATCH net-next v5 1/5] mm: add a signature in struct page
In reply to Matthew WilcoxQuoted 4 lines · Matthew Wilcox
I feel like I want to document the pfmemalloc bit in
mm_types.h, but I don't have a concrete suggestion yet.
Maybe simply:
/* Bit zero is set
* Bit one if pfmemalloc page
*/
unsigned long compound_head;
Regards,
Signature · 1 line
per aspera ad upstream