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 3/5] tcp, flow: Replace per-connection in_epoll flag with epollfd in flow_common
Date: Wed, 8 Oct 2025 11:24:35 +1100	[thread overview]
Message-ID: <aOWvQwQiDrI94_ZR@zatzit> (raw)
In-Reply-To: <795ada45-d8ec-4ede-9b2e-54b5e1a50267@redhat.com>

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

On Tue, Oct 07, 2025 at 03:26:23PM +0200, Laurent Vivier wrote:
> On 07/10/2025 08:07, David Gibson wrote:
> > On Fri, Oct 03, 2025 at 05:27:15PM +0200, Laurent Vivier wrote:
> > > The in_epoll boolean flag in tcp_tap_conn and tcp_splice_conn only tracked
> > > whether a connection was registered with epoll, not which epoll instance.
> > > This limited flexibility for future multi-epoll support.
> > > 
> > > Replace the boolean with an epollfd field in flow_common that serves dual
> > > purpose: zero indicates not registered (replacing in_epoll=false), non-zero
> > 
> > Don't use 0, since that's a valid fd.
> > 
> > > stores the actual epoll fd (replacing in_epoll=true).
> > 
> > I am a bit nervous about adding 31-bits to every flow, since I think
> > we're fairly close to a cacheline threshold.
> > 
> > I'm not sure we really can add any less to flow_common, though, given
> > alignment.
> > 
> > Then again... we probably don't need 8 bites each for TYPE and STATE,
> > so those could be packed tighter.  Then we could use a limited-bits
> > index into a table of epollfds, rather than a raw fd.  Much uglier,
> > but maybe worth it?
> > 
> 
> I tried the epollfds table. But it introduces complexity and a new shared
> data structure that we will need to manage correctly in the case of
> multithreading. I don't think it's the way to follow...

I was assuming it would be a write-once data structure, meaning
multithreaded management shouldn't be too hard.  But ok.

> The epollfds will be open at startup (we have already one: c->epollfd) and
> their number will depend on the number of threads/queues (the maximum number
> of virtqueues for QEMU is 65536 but the number of queues is generally
> configured to match the number of vCPU). And we can guess the file
> descriptor will be allocated in order. So I think we can expect to fit in an
> 8-bit.

Right, I guess it will.  I don't love relying on that, but it's
certainly an option.

> In passt I'm setting the maximum number of virtqueues to 64, that
> will limit also the number of epollfd.
> 
> Thanks,
> Laurent
> 
> 

-- 
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-08  0:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-03 15:27 [PATCH 0/5] Refactor epoll handling in preparation for multithreading Laurent Vivier
2025-10-03 15:27 ` [PATCH 1/5] util: Simplify epoll_del() interface to take epollfd directly Laurent Vivier
2025-10-07  5:26   ` David Gibson
2025-10-03 15:27 ` [PATCH 2/5] util: Move epoll registration out of sock_l4_sa() Laurent Vivier
2025-10-07  5:57   ` David Gibson
2025-10-03 15:27 ` [PATCH 3/5] tcp, flow: Replace per-connection in_epoll flag with epollfd in flow_common Laurent Vivier
2025-10-07  6:07   ` David Gibson
2025-10-07  9:51     ` Stefano Brivio
2025-10-07 12:07       ` Laurent Vivier
2025-10-07 12:15         ` Stefano Brivio
2025-10-08  0:12           ` David Gibson
2025-10-07 13:26     ` Laurent Vivier
2025-10-08  0:24       ` David Gibson [this message]
2025-10-03 15:27 ` [PATCH 4/5] icmp: Use epollfd from flow_common structure Laurent Vivier
2025-10-03 15:27 ` [PATCH 5/5] udp: " Laurent Vivier

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=aOWvQwQiDrI94_ZR@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).