Re: [RFC PATCH v3 13/20] io_uring: implement pp memory provider for zc rx

Pavel Begunkov
2023-12-20T00:44:53Z

On 12/19/23 23:44, Mina Almasry wrote:
> On Tue, Dec 19, 2023 at 1:04 PM David Wei <dw@davidwei.uk> wrote:
>>
>> From: Pavel Begunkov <asml.silence@gmail.com>
>>
>> We're adding a new pp memory provider to implement io_uring zerocopy
>> receive. It'll be "registered" in pp and used in later paches.
>>
>> The typical life cycle of a buffer goes as follows: first it's allocated
>> to a driver with the initial refcount set to 1. The drivers fills it
>> with data, puts it into an skb and passes down the stack, where it gets
>> queued up to a socket. Later, a zc io_uring request will be receiving
>> data from the socket from a task context. At that point io_uring will
>> tell the userspace that this buffer has some data by posting an
>> appropriate completion. It'll also elevating the refcount by
>> IO_ZC_RX_UREF, so the buffer is not recycled while userspace is reading
>
> After you rebase to the latest RFC, you will want to elevante the
> [pp|n]iov->pp_ref_count, rather than the non-existent ppiov->refcount.
> I do the same thing for devmem TCP.
>
>> the data. When the userspace is done with the buffer it should return it
>> back to io_uring by adding an entry to the buffer refill ring. When
>> necessary io_uring will poll the refill ring, compare references
>> including IO_ZC_RX_UREF and reuse the buffer.
>>
>> Initally, all buffers are placed in a spinlock protected ->freelist.
>> It's a slow path stash, where buffers are considered to be unallocated
>> and not exposed to core page pool. On allocation, pp will first try
>> all its caches, and the ->alloc_pages callback if everything else
>> failed.
>>
>> The hot path for io_pp_zc_alloc_pages() is to grab pages from the refill
>> ring. The consumption from the ring is always done in the attached napi
>> context, so no additional synchronisation required. If that fails we'll
>> be getting buffers from the ->freelist.
>>
>> Note: only ->freelist are considered unallocated for page pool, so we
>> only add pages_state_hold_cnt when allocating from there. Subsequently,
>> as page_pool_return_page() and others bump the ->pages_state_release_cnt
>> counter, io_pp_zc_release_page() can only use ->freelist, which is not a
>> problem as it's not a slow path.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>> Signed-off-by: David Wei <dw@davidwei.uk>
>> ---
>> include/linux/io_uring/net.h | 5 +
>> io_uring/zc_rx.c | 204 +++++++++++++++++++++++++++++++++++
>> io_uring/zc_rx.h | 6 ++
>> 3 files changed, 215 insertions(+)
>>
>> diff --git a/include/linux/io_uring/net.h b/include/linux/io_uring/net.h
>> index d994d26116d0..13244ae5fc4a 100644
>> --- a/include/linux/io_uring/net.h
>> +++ b/include/linux/io_uring/net.h
>> @@ -13,6 +13,11 @@ struct io_zc_rx_buf {
>> };
>>
>> #if defined(CONFIG_IO_URING)
>> +
>> +#if defined(CONFIG_PAGE_POOL)
>> +extern const struct pp_memory_provider_ops io_uring_pp_zc_ops;
>> +#endif
>> +
>> int io_uring_cmd_sock(struct io_uring_cmd *cmd, unsigned int issue_flags);
>>
>> #else
>> diff --git a/io_uring/zc_rx.c b/io_uring/zc_rx.c
>> index 1e656b481725..ff1dac24ac40 100644
>> --- a/io_uring/zc_rx.c
>> +++ b/io_uring/zc_rx.c
>> @@ -6,6 +6,7 @@
>> #include <linux/io_uring.h>
>> #include <linux/netdevice.h>
>> #include <linux/nospec.h>
>> +#include <trace/events/page_pool.h>
>>
>> #include <uapi/linux/io_uring.h>
>>
>> @@ -387,4 +388,207 @@ int io_register_zc_rx_sock(struct io_ring_ctx *ctx,
>> return 0;
>> }
>>
>> +static inline struct io_zc_rx_buf *io_iov_to_buf(struct page_pool_iov *iov)
>> +{
>> + return container_of(iov, struct io_zc_rx_buf, ppiov);
>> +}
>> +
>> +static inline unsigned io_buf_pgid(struct io_zc_rx_pool *pool,
>> + struct io_zc_rx_buf *buf)
>> +{
>> + return buf - pool->bufs;
>> +}
>> +
>> +static __maybe_unused void io_zc_rx_get_buf_uref(struct io_zc_rx_buf *buf)
>> +{
>> + refcount_add(IO_ZC_RX_UREF, &buf->ppiov.refcount);
>> +}
>> +
>> +static bool io_zc_rx_put_buf_uref(struct io_zc_rx_buf *buf)
>> +{
>> + if (page_pool_iov_refcount(&buf->ppiov) < IO_ZC_RX_UREF)
>> + return false;
>> +
>> + return page_pool_iov_sub_and_test(&buf->ppiov, IO_ZC_RX_UREF);
>> +}
>> +
>> +static inline struct page *io_zc_buf_to_pp_page(struct io_zc_rx_buf *buf)
>> +{
>> + return page_pool_mangle_ppiov(&buf->ppiov);
>> +}
>> +
>> +static inline void io_zc_add_pp_cache(struct page_pool *pp,
>> + struct io_zc_rx_buf *buf)
>> +{
>> + refcount_set(&buf->ppiov.refcount, 1);
>> + pp->alloc.cache[pp->alloc.count++] = io_zc_buf_to_pp_page(buf);
>> +}
>> +
>> +static inline u32 io_zc_rx_rqring_entries(struct io_zc_rx_ifq *ifq)
>> +{
>> + struct io_rbuf_ring *ring = ifq->ring;
>> + u32 entries;
>> +
>> + entries = smp_load_acquire(&ring->rq.tail) - ifq->cached_rq_head;
>> + return min(entries, ifq->rq_entries);
>> +}
>> +
>> +static void io_zc_rx_ring_refill(struct page_pool *pp,
>> + struct io_zc_rx_ifq *ifq)
>> +{
>> + unsigned int entries = io_zc_rx_rqring_entries(ifq);
>> + unsigned int mask = ifq->rq_entries - 1;
>> + struct io_zc_rx_pool *pool = ifq->pool;
>> +
>> + if (unlikely(!entries))
>> + return;
>> +
>> + while (entries--) {
>> + unsigned int rq_idx = ifq->cached_rq_head++ & mask;
>> + struct io_uring_rbuf_rqe *rqe = &ifq->rqes[rq_idx];
>> + u32 pgid = rqe->off / PAGE_SIZE;
>> + struct io_zc_rx_buf *buf = &pool->bufs[pgid];
>> +
>> + if (!io_zc_rx_put_buf_uref(buf))
>> + continue;
>> + io_zc_add_pp_cache(pp, buf);
>> + if (pp->alloc.count >= PP_ALLOC_CACHE_REFILL)
>> + break;
>> + }
>> + smp_store_release(&ifq->ring->rq.head, ifq->cached_rq_head);
>> +}
>> +
>> +static void io_zc_rx_refill_slow(struct page_pool *pp, struct io_zc_rx_ifq *ifq)
>> +{
>> + struct io_zc_rx_pool *pool = ifq->pool;
>> +
>> + spin_lock_bh(&pool->freelist_lock);
>> + while (pool->free_count && pp->alloc.count < PP_ALLOC_CACHE_REFILL) {
>> + struct io_zc_rx_buf *buf;
>> + u32 pgid;
>> +
>> + pgid = pool->freelist[--pool->free_count];
>> + buf = &pool->bufs[pgid];
>> +
>> + io_zc_add_pp_cache(pp, buf);
>> + pp->pages_state_hold_cnt++;
>> + trace_page_pool_state_hold(pp, io_zc_buf_to_pp_page(buf),
>> + pp->pages_state_hold_cnt);
>> + }
>> + spin_unlock_bh(&pool->freelist_lock);
>> +}
>> +
>> +static void io_zc_rx_recycle_buf(struct io_zc_rx_pool *pool,
>> + struct io_zc_rx_buf *buf)
>> +{
>> + spin_lock_bh(&pool->freelist_lock);
>> + pool->freelist[pool->free_count++] = io_buf_pgid(pool, buf);
>> + spin_unlock_bh(&pool->freelist_lock);
>> +}
>> +
>> +static struct page *io_pp_zc_alloc_pages(struct page_pool *pp, gfp_t gfp)
>> +{
>> + struct io_zc_rx_ifq *ifq = pp->mp_priv;
>> +
>> + /* pp should already be ensuring that */
>> + if (unlikely(pp->alloc.count))
>> + goto out_return;
>> +
>> + io_zc_rx_ring_refill(pp, ifq);
>> + if (likely(pp->alloc.count))
>> + goto out_return;
>> +
>> + io_zc_rx_refill_slow(pp, ifq);
>> + if (!pp->alloc.count)
>> + return NULL;
>> +out_return:
>> + return pp->alloc.cache[--pp->alloc.count];
>> +}
>> +
>> +static bool io_pp_zc_release_page(struct page_pool *pp, struct page *page)
>> +{
>> + struct io_zc_rx_ifq *ifq = pp->mp_priv;
>> + struct page_pool_iov *ppiov;
>> +
>> + if (WARN_ON_ONCE(!page_is_page_pool_iov(page)))
>> + return false;
>> +
>> + ppiov = page_to_page_pool_iov(page);
>> +
>> + if (!page_pool_iov_sub_and_test(ppiov, 1))
>> + return false;
>> +
>> + io_zc_rx_recycle_buf(ifq->pool, io_iov_to_buf(ppiov));
>> + return true;
>> +}
>> +
>> +static void io_pp_zc_scrub(struct page_pool *pp)
>> +{
>> + struct io_zc_rx_ifq *ifq = pp->mp_priv;
>> + struct io_zc_rx_pool *pool = ifq->pool;
>> + struct io_zc_rx_buf *buf;
>> + int i;
>> +
>> + for (i = 0; i < pool->nr_bufs; i++) {
>> + buf = &pool->bufs[i];
>> +
>> + if (io_zc_rx_put_buf_uref(buf)) {
>> + /* just return it to the page pool, it'll clean it up */
>> + refcount_set(&buf->ppiov.refcount, 1);
>> + page_pool_iov_put_many(&buf->ppiov, 1);
>> + }
>> + }
>> +}
>> +
>
> I'm unsure about this. So scrub forcibly frees the pending data? Why
> does this work? Can't the application want to read this data even
> though the page_pool is destroyed?

It only affects buffers that were given back to the userspace
and are still there. Even if it scrubs like that, the completions are
still visible to the user, there are pointing to correct buffers,
which are still supposed to be mapped well. Yes, we return them earlier
to the kernel, but since reallocation should not be possible at that
point the data in the buffers would stay correct. There might be
problems with copy fallback, but it'll need to improve anyway,
I'm keeping an eye on it

In any case, I'd say if page pool is destroyed while we're still
using it, I'd say something is going really wrong and the user should
terminate all of it, but that raises a question in what valid cases
the kernel might decide to reallocate pp (device reconfiguration),
and what the application is supposed to do about it.

> AFAIK the page_pool being destroyed doesn't mean we can free the
> pages/niovs in it. The niovs that were in it can be waiting on the
> receive queue for the application to call recvmsg() on it. Does
> io_uring work differently such that you're able to force-free the
> ppiovs/niovs?

If a buffer is used by the stack, the stack will hold a reference.
We're not just blindly freeing them here, only dropping the userspace
reference. An analogy for devmem would to remove all involved buffers
from dont_need xarrays (also dropping a reference IIRC).

--
Pavel Begunkov