public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: David Wei <dw@davidwei.uk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH v4 2/6] io_uring/zcrx: return error from io_zcrx_map_area_*
Date: Wed, 2 Jul 2025 15:27:17 -0700	[thread overview]
Message-ID: <bf0aac47-723e-40eb-a280-f8868edf9d26@davidwei.uk> (raw)
In-Reply-To: <42668e82be3a84b07ee8fc76d1d6d5ac0f137fe5.1751466461.git.asml.silence@gmail.com>

On 2025-07-02 07:29, Pavel Begunkov wrote:
> io_zcrx_map_area_*() helpers return the number of processed niovs, which
> we use to unroll some of the mappings for user memory areas. It's
> unhandy, and dmabuf doesn't care about it. Return an error code instead
> and move failure partial unmapping into io_zcrx_map_area_umem().
> 
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
>   io_uring/zcrx.c | 27 ++++++++++++++-------------
>   1 file changed, 14 insertions(+), 13 deletions(-)
> 
> diff --git a/io_uring/zcrx.c b/io_uring/zcrx.c
> index 99a253c1c6c5..2cde88988260 100644
> --- a/io_uring/zcrx.c
> +++ b/io_uring/zcrx.c

...

> @@ -254,29 +254,30 @@ static int io_zcrx_map_area_umem(struct io_zcrx_ifq *ifq, struct io_zcrx_area *a
>   			break;
>   		}
>   	}
> -	return i;
> +
> +	if (i != area->nia.num_niovs) {
> +		__io_zcrx_unmap_area(ifq, area, i);
> +		return -EINVAL;
> +	}
> +	return 0;
>   }

Does io_release_dmabuf() still need to be called in
io_zcrx_map_area_dmabuf() in case of failure, if say
net_mp_niov_set_dma_addr() fails in the loop?

  reply	other threads:[~2025-07-02 22:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 14:29 [PATCH v4 0/6] zcrx huge pages support Vol 1 Pavel Begunkov
2025-07-02 14:29 ` [PATCH v4 1/6] io_uring/zcrx: always pass page to io_zcrx_copy_chunk Pavel Begunkov
2025-07-02 22:32   ` David Wei
2025-07-02 14:29 ` [PATCH v4 2/6] io_uring/zcrx: return error from io_zcrx_map_area_* Pavel Begunkov
2025-07-02 22:27   ` David Wei [this message]
2025-07-02 22:50     ` Pavel Begunkov
2025-07-02 23:20       ` David Wei
2025-07-02 14:29 ` [PATCH v4 3/6] io_uring/zcrx: introduce io_populate_area_dma Pavel Begunkov
2025-07-02 23:13   ` David Wei
2025-07-02 14:29 ` [PATCH v4 4/6] io_uring/zcrx: allocate sgtable for umem areas Pavel Begunkov
2025-07-02 23:16   ` David Wei
2025-07-02 14:29 ` [PATCH v4 5/6] io_uring/zcrx: assert area type in io_zcrx_iov_page Pavel Begunkov
2025-07-02 14:29 ` [PATCH v4 6/6] io_uring/zcrx: prepare fallback for larger pages Pavel Begunkov
2025-07-02 23:12 ` [PATCH v4 0/6] zcrx huge pages support Vol 1 David Wei
2025-07-02 23:51   ` Pavel Begunkov
2025-07-08 18:00 ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bf0aac47-723e-40eb-a280-f8868edf9d26@davidwei.uk \
    --to=dw@davidwei.uk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox