public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Haiyue Wang <haiyuewa@163.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing v1 1/2] examples/zcrx: Use PAGE_SIZE for ring refill alignment
Date: Sat, 19 Apr 2025 06:51:59 -0600	[thread overview]
Message-ID: <af78093c-9cf9-4e71-8d89-029ab460fab9@kernel.dk> (raw)
In-Reply-To: <20250419095732.4076-1-haiyuewa@163.com>

On 4/19/25 3:57 AM, Haiyue Wang wrote:
> According to the 'Create refill ring' section in [1], use the macro
> PAGE_SIZE instead of 4096 hard code number.
> 
> [1]: https://www.kernel.org/doc/html/latest/networking/iou-zcrx.html
> 
> Signed-off-by: Haiyue Wang <haiyuewa@163.com>
> ---
>  examples/zcrx.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/examples/zcrx.c b/examples/zcrx.c
> index 8393cfe..c96bbfe 100644
> --- a/examples/zcrx.c
> +++ b/examples/zcrx.c
> @@ -66,7 +66,7 @@ static inline size_t get_refill_ring_size(unsigned int rq_entries)
>  	ring_size = rq_entries * sizeof(struct io_uring_zcrx_rqe);
>  	/* add space for the header (head/tail/etc.) */
>  	ring_size += PAGE_SIZE;
> -	return T_ALIGN_UP(ring_size, 4096);
> +	return T_ALIGN_UP(ring_size, PAGE_SIZE);
>  }
>  
>  static void setup_zcrx(struct io_uring *ring)

Well, in that same file:

#define PAGE_SIZE (4096)         

so this won't really fix anything. Examples or test code
should use:

sysconf(_SC_PAGESIZE)

to get the page size at runtime.

-- 
Jens Axboe

  parent reply	other threads:[~2025-04-19 12:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-19  9:57 [PATCH liburing v1 1/2] examples/zcrx: Use PAGE_SIZE for ring refill alignment Haiyue Wang
2025-04-19  9:57 ` [PATCH liburing v1 2/2] .gitignore: Add `examples/zcrx` Haiyue Wang
2025-04-19 12:51 ` Jens Axboe [this message]
2025-04-19 13:13   ` [PATCH liburing v1 1/2] examples/zcrx: Use PAGE_SIZE for ring refill alignment Haiyue Wang
2025-04-19 12:52 ` (subset) " 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=af78093c-9cf9-4e71-8d89-029ab460fab9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=haiyuewa@163.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