public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/6] RFC: Clean up tap-side event handling
Date: Tue, 3 Sep 2024 21:25:54 +0200	[thread overview]
Message-ID: <20240903212554.036da194@elisabeth> (raw)
In-Reply-To: <20240903120235.1688429-1-david@gibson.dropbear.id.au>

On Tue,  3 Sep 2024 22:02:29 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> This is a draft patch working towards adding EPOLLOUT handling to the
> tap code, which could then be used to "unstick" flows which have
> unsent data from the socket side.  For now that's just a stub, but
> makes what I think are some worthwhile cleanups to the tap side event
> handling in the meantime.

Except for the issue in 3/6 and nits elsewhere, it all makes sense and
tap-side EPOLLOUT handling is definitely going to be an improvement.

I wonder if it's the right moment for this kind of series, though, in
terms of future bisections, as long as we're grappling with
https://github.com/containers/podman/issues/23686 and
https://bugs.passt.top/show_bug.cgi?id=94. Assuming, of course, that
this series doesn't fix anything.

That is, once/if we come up with fixes for those, as they might involve
setting different event masks, I'd rather have those in *before* this
series, to avoid further noise in case we manage to break something
else with those hypothetical fixes.

-- 
Stefano


  parent reply	other threads:[~2024-09-03 19:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 12:02 [PATCH 0/6] RFC: Clean up tap-side event handling David Gibson
2024-09-03 12:02 ` [PATCH 1/6] tap: Split out handling of EPOLLIN events David Gibson
2024-09-03 19:25   ` Stefano Brivio
2024-09-04  1:17     ` David Gibson
2024-09-03 12:02 ` [PATCH 2/6] tap: Improve handling of EINTR in tap_passt_input() David Gibson
2024-09-03 19:25   ` Stefano Brivio
2024-09-04  1:30     ` David Gibson
2024-09-03 12:02 ` [PATCH 3/6] tap: Restructure in tap_pasta_input() David Gibson
2024-09-03 19:25   ` Stefano Brivio
2024-09-04  1:33     ` David Gibson
2024-09-03 12:02 ` [PATCH 4/6] tap: Don't risk truncating frames on full buffer " David Gibson
2024-09-03 19:25   ` Stefano Brivio
2024-09-04  1:33     ` David Gibson
2024-09-03 12:02 ` [PATCH 5/6] tap: Re-introduce EPOLLET for tap connections David Gibson
2024-09-03 19:25   ` Stefano Brivio
2024-09-04  1:36     ` David Gibson
2024-09-03 12:02 ` [PATCH 6/6] tap: Stub EPOLLOUT handling David Gibson
2024-09-03 19:25 ` Stefano Brivio [this message]
2024-09-04  3:17   ` [PATCH 0/6] RFC: Clean up tap-side event handling David Gibson
2024-09-04 17:19     ` Stefano Brivio
2024-09-05  0:35       ` David Gibson
2024-09-05  8:32         ` Stefano Brivio
2024-09-05 11:33           ` Stefano Brivio

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=20240903212554.036da194@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --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).