On Wed, Sep 25, 2024 at 1:03 AM Yunsheng Lin <linyunsh...@huawei.com> wrote: > > Networking driver with page_pool support may hand over page > still with dma mapping to network stack and try to reuse that > page after network stack is done with it and passes it back > to page_pool to avoid the penalty of dma mapping/unmapping. > With all the caching in the network stack, some pages may be > held in the network stack without returning to the page_pool > soon enough, and with VF disable causing the driver unbound, > the page_pool does not stop the driver from doing it's > unbounding work, instead page_pool uses workqueue to check > if there is some pages coming back from the network stack > periodically, if there is any, it will do the dma unmmapping > related cleanup work. > > As mentioned in [1], attempting DMA unmaps after the driver > has already unbound may leak resources or at worst corrupt > memory. Fundamentally, the page pool code cannot allow DMA > mappings to outlive the driver they belong to. > > Currently it seems there are at least two cases that the page > is not released fast enough causing dma unmmapping done after > driver has already unbound: > 1. ipv4 packet defragmentation timeout: this seems to cause > delay up to 30 secs. > 2. skb_defer_free_flush(): this may cause infinite delay if > there is no triggering for net_rx_action(). >
I think additionally this is dependent on user behavior, right? AFAIU, frags allocated by the page_pool will remain in the socket receive queue until the user calls recvmsg(), and AFAIU they are stuck there arbitrarily long. > In order not to do the dma unmmapping after driver has already > unbound and stall the unloading of the networking driver, add > the pool->items array to record all the pages including the ones > which are handed over to network stack, so the page_pool can > do the dma unmmapping for those pages when page_pool_destroy() > is called. One thing I could not understand from looking at the code: if the items array is in the struct page_pool, why do you need to modify the page_pool entry in the struct page and in the struct net_iov? I think the code could be made much simpler if you can remove these changes, and you wouldn't need to modify the public api of the page_pool. > As the pool->items need to be large enough to avoid > performance degradation, add a 'item_full' stat to indicate the > allocation failure due to unavailability of pool->items. > I'm not sure there is any way to size the pool->items array correctly. Can you use a data structure here that can grow? Linked list or xarray? AFAIU what we want is when the page pool allocates a netmem it will add the netmem to the items array, and when the pp releases a netmem it will remove it from the array. Both of these operations are slow paths, right? So the performance of a data structure more complicated than an array may be ok. bench_page_pool_simple will tell for sure. > Note, the devmem patchset seems to make the bug harder to fix, > and may make backporting harder too. As there is no actual user > for the devmem and the fixing for devmem is unclear for now, > this patch does not consider fixing the case for devmem yet. > net_iovs don't hit this bug, dma_unmap_page_attrs() is never called on them, so no special handling is needed really. However for code quality reasons lets try to minimize the number of devmem or memory provider checks in the code, if possible. -- Thanks, Mina
