From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 07/13] epoll: Fold sock_handler into general switch on epoll event fd
Date: Fri, 11 Aug 2023 13:11:37 +1000 [thread overview]
Message-ID: <ZNWm6dFJjM+qTxzp@zatzit> (raw)
In-Reply-To: <20230810214841.3d148ba0@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 3384 bytes --]
On Thu, Aug 10, 2023 at 09:49:37PM +0200, Stefano Brivio wrote:
> On Thu, 10 Aug 2023 12:33:09 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > When we process events from epoll_wait(), we check for a number of special
> > cases before calling sock_handler() which then dispatches based on the
> > protocol type of the socket in the event.
> >
> > Fold these cases together into a single switch on the fd type recorded in
> > the epoll data field.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > passt.c | 54 +++++++++++++++++++++++++++---------------------------
> > 1 file changed, 27 insertions(+), 27 deletions(-)
> >
> > diff --git a/passt.c b/passt.c
> > index 45e9fbf..665262b 100644
> > --- a/passt.c
> > +++ b/passt.c
> > @@ -64,29 +64,6 @@ char *epoll_type_str[EPOLL_TYPE_MAX + 1] = {
> > [EPOLL_TYPE_TAP] = "tap device",
> > };
> >
> > -/**
> > - * sock_handler() - Event handler for L4 sockets
> > - * @c: Execution context
> > - * @ref: epoll reference
> > - * @events: epoll events
> > - * @now: Current timestamp
> > - */
> > -static void sock_handler(struct ctx *c, union epoll_ref ref,
> > - uint32_t events, const struct timespec *now)
> > -{
> > - trace("%s: packet from %s %i (events: 0x%08x)",
> > - c->mode == MODE_PASST ? "passt" : "pasta",
> > - EPOLL_TYPE_STR(ref.type), ref.fd, events);
> > -
> > - if (!c->no_tcp && ref.type == EPOLL_TYPE_TCP)
> > - tcp_sock_handler(c, ref, events, now);
> > - else if (!c->no_udp && ref.type == EPOLL_TYPE_UDP)
> > - udp_sock_handler(c, ref, events, now);
> > - else if (!c->no_icmp &&
> > - (ref.type == EPOLL_TYPE_ICMP || ref.type == EPOLL_TYPE_ICMPV6))
> > - icmp_sock_handler(c, ref, events, now);
> > -}
> > -
> > /**
> > * post_handler() - Run periodic and deferred tasks for L4 protocol handlers
> > * @c: Execution context
> > @@ -330,13 +307,36 @@ loop:
> >
> > for (i = 0; i < nfds; i++) {
> > union epoll_ref ref = *((union epoll_ref *)&events[i].data.u64);
> > + uint32_t eventmask = events[i].events;
> >
> > - if (ref.type == EPOLL_TYPE_TAP)
> > + trace("%s: epoll event on %s %i (events: 0x%08x)",
> > + c.mode == MODE_PASST ? "passt" : "pasta",
> > + EPOLL_TYPE_STR(ref.type), ref.fd, events);
>
> Gah, sorry I missed this earlier, but covscan reported it -- you
> probably wanted to pass 'eventmask' to trace().
Oops, good catch. Fixed for a new spin
> Actually, a long time ago, I was pondering about a macro that would
> print constants' names ("EPOLLIN", etc.) instead, but then I thought
> that once you remember the values from <sys/epoll.h>, hex values might
> be a bit easier on eyes when you're digging through thousands of
> them... or maybe not. I don't know actually.
I'm inclined to leave it as hex for simplicity. The fact that we
could have multiple events means it's not really simple macro
territory; we'd have to format a bunch of stuff. I don't think that's
worth bothering with for a trace message unless we repeatedly find
it's making our debugging more difficult, which hasn't happened so
far.
--
David Gibson | 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 --]
next prev parent reply other threads:[~2023-08-11 3:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 2:33 [PATCH v2 00/13] Clean up to tap errors and epoll dispatch David Gibson
2023-08-10 2:33 ` [PATCH v2 01/13] tap: Clean up tap reset path David Gibson
2023-08-10 2:33 ` [PATCH v2 02/13] tap: Clean up behaviour for errors on listening Unix socket David Gibson
2023-08-10 2:33 ` [PATCH v2 03/13] tap: Fold reset handling into tap_handler_pasta() David Gibson
2023-08-10 2:33 ` [PATCH v2 04/13] tap: Fold reset handling into tap_handler_passt() David Gibson
2023-08-10 19:49 ` Stefano Brivio
2023-08-11 3:07 ` David Gibson
2023-08-10 2:33 ` [PATCH v2 05/13] epoll: Generalize epoll_ref to cover things other than sockets David Gibson
2023-08-10 2:33 ` [PATCH v2 06/13] epoll: Always use epoll_ref for the epoll data variable David Gibson
2023-08-10 2:33 ` [PATCH v2 07/13] epoll: Fold sock_handler into general switch on epoll event fd David Gibson
2023-08-10 19:49 ` Stefano Brivio
2023-08-11 3:11 ` David Gibson [this message]
2023-08-10 2:33 ` [PATCH v2 08/13] epoll: Split handling of ICMP and ICMPv6 sockets David Gibson
2023-08-10 2:33 ` [PATCH v2 09/13] epoll: Tiny cleanup to udp_sock_handler() David Gibson
2023-08-10 2:33 ` [PATCH v2 10/13] epoll: Split handling of TCP timerfds into its own handler function David Gibson
2023-08-10 2:33 ` [PATCH v2 11/13] epoll: Split handling of listening TCP sockets into their own handler David Gibson
2023-08-10 2:33 ` [PATCH v2 12/13] epoll: Split listening Unix domain socket into its own type David Gibson
2023-08-10 2:33 ` [PATCH v2 13/13] epoll: Use different epoll types for passt and pasta tap fds 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=ZNWm6dFJjM+qTxzp@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.com \
/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).