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 v3 00/13] Clean up to tap errors and epoll dispatch
Date: Sun, 13 Aug 2023 18:31:35 +0200	[thread overview]
Message-ID: <20230813183135.738a7e7b@elisabeth> (raw)
In-Reply-To: <20230811051229.343838-1-david@gibson.dropbear.id.au>

On Fri, 11 Aug 2023 15:12:16 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> Getting from an epoll event to the relevant handler function is
> currently several levels of functions and tests.  This series
> simplifies this to be pretty close to a single switch on a value in
> the epoll ref dispatching directly to the appropriate handler.
> 
> Doing this requires some preliminary cleaning up of the handling of
> errors or disconnects on the tap device.
> 
> Changes since v2:
>  * Removed a (pre-existing) redundant close() and EPOLL_CTL_DEL in one
>    of the tap reset paths
>  * Fixed incorrect parameter to trace() message
> 
> Changes since v1:
>  * Give listening TCP sockets their own reference type
>  * Fold "tap reset" series into this one
> 
> Changes since v2 of tap reset series:
>  * More thorough cleanup of handling error events on the listening
>    Unix socket.
> Changes since v1 of the tap reset series:
>  * Two extra patches that further clean up the reset path

Applied, thanks!

-- 
Stefano


      parent reply	other threads:[~2023-08-13 16:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11  5:12 [PATCH v3 00/13] Clean up to tap errors and epoll dispatch David Gibson
2023-08-11  5:12 ` [PATCH v3 01/13] tap: Clean up tap reset path David Gibson
2023-08-11  5:12 ` [PATCH v3 02/13] tap: Clean up behaviour for errors on listening Unix socket David Gibson
2023-08-11  5:12 ` [PATCH v3 03/13] tap: Fold reset handling into tap_handler_pasta() David Gibson
2023-08-11  5:12 ` [PATCH v3 04/13] tap: Fold reset handling into tap_handler_passt() David Gibson
2023-08-11  5:12 ` [PATCH v3 05/13] epoll: Generalize epoll_ref to cover things other than sockets David Gibson
2023-08-11  5:12 ` [PATCH v3 06/13] epoll: Always use epoll_ref for the epoll data variable David Gibson
2023-08-11  5:12 ` [PATCH v3 07/13] epoll: Fold sock_handler into general switch on epoll event fd David Gibson
2023-08-11  5:12 ` [PATCH v3 08/13] epoll: Split handling of ICMP and ICMPv6 sockets David Gibson
2023-08-11  5:12 ` [PATCH v3 09/13] epoll: Tiny cleanup to udp_sock_handler() David Gibson
2023-08-11  5:12 ` [PATCH v3 10/13] epoll: Split handling of TCP timerfds into its own handler function David Gibson
2023-08-11  5:12 ` [PATCH v3 11/13] epoll: Split handling of listening TCP sockets into their own handler David Gibson
2023-08-11  5:12 ` [PATCH v3 12/13] epoll: Split listening Unix domain socket into its own type David Gibson
2023-08-11  5:12 ` [PATCH v3 13/13] epoll: Use different epoll types for passt and pasta tap fds David Gibson
2023-08-13 16:31 ` Stefano Brivio [this message]

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