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 7/8] tcp: Protect init socket pools with mutex for thread safety
Date: Thu, 2 Jul 2026 12:59:47 +1000	[thread overview]
Message-ID: <akXUI8J8SeIkXL0B@zatzit> (raw)
In-Reply-To: <20260616171052.3785909-8-lvivier@redhat.com>

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

On Tue, Jun 16, 2026 at 07:10:51PM +0200, Laurent Vivier wrote:
> The pre-opened socket pools init_sock_pool4/6 are consumed by
> tcp_conn_pool_sock() when creating new connections from any worker
> thread, and refilled by tcp_sock_refill_pool() from tcp_timer() in
> post_handler(). These can run concurrently on different threads.
> 
> Add a mutex protecting both operations in tcp_conn_sock() and
> tcp_sock_refill_init(), where init namespace pools are accessed.

I wonder if we might be better off with a per-qpair/thread socket pool
instead of a mutexed common pool.  The obvious tradeoff would be that
the pool is smaller so a thread could run out of sockets while we
still have some available on another thread.  But, having a common
pool only gains us there if the mutex lock is significantly cheaper
than the system calls to refill the pool.  That might be the case, but
I'm not certain.

> 
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
>  tcp.c | 10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/tcp.c b/tcp.c
> index 955012355d69..019340c1c348 100644
> --- a/tcp.c
> +++ b/tcp.c
> @@ -293,6 +293,7 @@
>  #include <sys/uio.h>
>  #include <time.h>
>  #include <arpa/inet.h>
> +#include <pthread.h>
>  
>  #include <linux/sockios.h>
>  #include <linux/sock_diag.h>
> @@ -439,6 +440,7 @@ static socklen_t tcp_info_size;
>  /* Pools for pre-opened sockets (in init) */
>  int init_sock_pool4		[TCP_SOCK_POOL_SIZE];
>  int init_sock_pool6		[TCP_SOCK_POOL_SIZE];
> +static pthread_mutex_t sock_pool_lock = PTHREAD_MUTEX_INITIALIZER;
>  
>  /**
>   * conn_at_sidx() - Get TCP connection specific flow at given sidx
> @@ -1568,7 +1570,11 @@ int tcp_conn_sock(sa_family_t af)
>  	int *pool = af == AF_INET6 ? init_sock_pool6 : init_sock_pool4;
>  	int s;
>  
> -	if ((s = tcp_conn_pool_sock(pool)) >= 0)
> +	pthread_mutex_lock(&sock_pool_lock);
> +	s = tcp_conn_pool_sock(pool);
> +	pthread_mutex_unlock(&sock_pool_lock);
> +
> +	if (s >= 0)
>  		return s;
>  
>  	/* If the pool is empty we just open a new one without refilling the
> @@ -2857,6 +2863,7 @@ int tcp_sock_refill_pool(int pool[], sa_family_t af)
>   */
>  static void tcp_sock_refill_init(const struct ctx *c)
>  {
> +	pthread_mutex_lock(&sock_pool_lock);
>  	if (c->ifi4) {
>  		int rc = tcp_sock_refill_pool(init_sock_pool4, AF_INET);
>  		if (rc < 0)
> @@ -2869,6 +2876,7 @@ static void tcp_sock_refill_init(const struct ctx *c)
>  			warn("TCP: Error refilling IPv6 host socket pool: %s",
>  			     strerror_(-rc));
>  	}
> +	pthread_mutex_unlock(&sock_pool_lock);
>  }
>  
>  /**
> -- 
> 2.54.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:[~2026-07-02  3:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 17:10 [PATCH 0/8] multithreading: Prepare data structures for concurrent queue pair workers Laurent Vivier
2026-06-16 17:10 ` [PATCH 1/8] tap: Convert packet pools to per-queue-pair arrays for multiqueue Laurent Vivier
2026-06-29  9:59   ` David Gibson
2026-06-16 17:10 ` [PATCH 2/8] tap: Make L4 sequence pools per-qpair for thread safety Laurent Vivier
2026-07-02  2:27   ` David Gibson
2026-06-16 17:10 ` [PATCH 3/8] tcp: Make static buffers stack-local " Laurent Vivier
2026-07-02  2:32   ` David Gibson
2026-06-16 17:10 ` [PATCH 4/8] udp_vu: Make virtqueue " Laurent Vivier
2026-07-02  2:37   ` David Gibson
2026-06-16 17:10 ` [PATCH 5/8] flow: Make flow timer per-caller " Laurent Vivier
2026-07-02  2:49   ` David Gibson
2026-06-16 17:10 ` [PATCH 6/8] tcp: Make TCP timer state per-caller and guard global tasks Laurent Vivier
2026-07-02  2:55   ` David Gibson
2026-06-16 17:10 ` [PATCH 7/8] tcp: Protect init socket pools with mutex for thread safety Laurent Vivier
2026-07-02  2:59   ` David Gibson [this message]
2026-06-16 17:10 ` [PATCH 8/8] flow: Add mutex and per-qpair filtering to flow table operations Laurent Vivier
2026-07-02  3:03   ` 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=akXUI8J8SeIkXL0B@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).