public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v4 5/7] icmp: Use thread-based epoll management for ICMP flows
Date: Mon, 20 Oct 2025 12:35:54 +1100	[thread overview]
Message-ID: <aPWR-uDZ334-i6CK@zatzit> (raw)
In-Reply-To: <20251017103129.229412-6-lvivier@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

On Fri, Oct 17, 2025 at 12:31:27PM +0200, Laurent Vivier wrote:
> Store the thread number in the flow_common structure for ICMP ping
> flows using flow_epollfd_set() and retrieve the corresponding epoll
> file descriptor with flow_epollfd_get() instead of passing c->epollfd
> directly. This makes ICMP consistent with the recent TCP changes and
> follows the pattern established in previous commit.
> 
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
>  icmp.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/icmp.c b/icmp.c
> index 56dfac6c958e..baddd8e5aacb 100644
> --- a/icmp.c
> +++ b/icmp.c
> @@ -149,7 +149,7 @@ unexpected:
>  static void icmp_ping_close(const struct ctx *c,
>  			    const struct icmp_ping_flow *pingf)
>  {
> -	epoll_del(c->epollfd, pingf->sock);
> +	epoll_del(flow_epollfd(&pingf->f), pingf->sock);
>  	close(pingf->sock);
>  	flow_hash_remove(c, FLOW_SIDX(pingf, INISIDE));
>  }
> @@ -206,11 +206,13 @@ static struct icmp_ping_flow *icmp_ping_new(const struct ctx *c,
>  	if (pingf->sock > FD_REF_MAX)
>  		goto cancel;
>  
> +	flow_thread_set(&pingf->f, 0);
> +
>  	ref.type = EPOLL_TYPE_PING;
>  	ref.flowside = FLOW_SIDX(flow, TGTSIDE);
>  	ref.fd = pingf->sock;
>  
> -	if (epoll_add(c->epollfd, EPOLLIN, &ref) < 0) {
> +	if (epoll_add(flow_epollfd(&pingf->f), EPOLLIN, &ref) < 0) {
>  		close(pingf->sock);
>  		goto cancel;
>  	}
> -- 
> 2.51.0
> 

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-10-20  1:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 10:31 [PATCH v4 0/7] Refactor epoll handling in preparation for multithreading Laurent Vivier
2025-10-17 10:31 ` [PATCH v4 1/7] util: Simplify epoll_del() interface to take epollfd directly Laurent Vivier
2025-10-17 10:31 ` [PATCH v4 2/7] epoll_ctl: Extract epoll operations Laurent Vivier
2025-10-17 11:48   ` Stefano Brivio
2025-10-17 12:21     ` Laurent Vivier
2025-10-17 13:05       ` Stefano Brivio
2025-10-20  1:20   ` David Gibson
2025-10-21 11:52     ` Laurent Vivier
2025-10-22  0:58       ` David Gibson
2025-10-17 10:31 ` [PATCH v4 3/7] util: Move epoll registration out of sock_l4_sa() Laurent Vivier
2025-10-17 10:31 ` [PATCH v4 4/7] tcp, flow: Replace per-connection in_epoll flag with threadnb in flow_common Laurent Vivier
2025-10-17 17:43   ` Stefano Brivio
2025-10-21 13:13     ` Laurent Vivier
2025-10-20  1:34   ` David Gibson
2025-10-21 12:14     ` Laurent Vivier
2025-10-22  1:00       ` David Gibson
2025-10-17 10:31 ` [PATCH v4 5/7] icmp: Use thread-based epoll management for ICMP flows Laurent Vivier
2025-10-20  1:35   ` David Gibson [this message]
2025-10-17 10:31 ` [PATCH v4 6/7] udp: Use thread-based epoll management for UDP flows Laurent Vivier
2025-10-20  1:39   ` David Gibson
2025-10-17 10:31 ` [PATCH v4 7/7] passt: Move main event loop processing into passt_worker() Laurent Vivier
2025-10-17 17:43   ` Stefano Brivio
2025-10-20  1:43   ` David Gibson
2025-10-21  8:00     ` Laurent Vivier
2025-10-22  0:53       ` David Gibson
2025-10-22  6:49         ` Laurent Vivier
2025-10-23  1:24           ` David Gibson

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=aPWR-uDZ334-i6CK@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).