From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 6/8] udp: Unify udp_sock_handler_splice() with udp_sock_handler()
Date: Thu, 5 Jan 2023 15:25:28 +1100 [thread overview]
Message-ID: <Y7ZROA3iNvum7WSk@yekko> (raw)
In-Reply-To: <20230104184438.2e43da08@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1895 bytes --]
On Wed, Jan 04, 2023 at 06:44:38PM +0100, Stefano Brivio wrote:
> On Wed, 4 Jan 2023 16:44:24 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
[snip]
> > /**
> > * udp_update_hdr4() - Update headers for one IPv4 datagram
> > * @c: Execution context
> > @@ -944,32 +898,53 @@ void udp_sock_handler(const struct ctx *c, union epoll_ref ref, uint32_t events,
> > const struct timespec *now)
> > {
> > /* For not entirely clear reasons (data locality?) pasta gets
> > - * better throughput if we receive the datagrams one at a
> > - * time.
> > + * better throughput if we receive tap datagrams one at a
> > + * atime. For small splice datagrams throughput is slightly
> > + * better if we do batch, but it's slightly worse for large
> > + * splice datagrams. Since we don't know before we receive
> > + * whether we'll use tap or splice, always go one at a time
> > + * for pasta mode.
> > */
> > ssize_t n = (c->mode == MODE_PASST ? UDP_MAX_FRAMES : 1);
> > in_port_t dstport = ref.r.p.udp.udp.port;
> > bool v6 = ref.r.p.udp.udp.v6;
> > - struct mmsghdr *sock_mmh;
> > + struct mmsghdr *mmh_recv;
> > + unsigned int i, m;
> > + ssize_t n;
>
> This doesn't build, you're redefining 'n' after the new version of 4/8.
Wow, that was super sloppy of me, sorry. I'm going to blame not being
quite back into it after the holiday. For whatever reason my brain
just skipped over even the most rudimentary testing here.
> I could drop this on merge (the rest of the series would be ready to
> merge) but as you usually prefer to respin anyway, I'll wait for that.
Yeah, I'll send a respin short. Tested, this time :).
--
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-01-05 4:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 5:44 [PATCH v3 0/8] Don't use additional sockets for receiving "spliced" UDP communications David Gibson
2023-01-04 5:44 ` [PATCH v3 1/8] udp: Move sending pasta tap frames to the end of udp_sock_handler() David Gibson
2023-01-04 5:44 ` [PATCH v3 2/8] udp: Split sending to passt tap interface into separate function David Gibson
2023-01-04 5:44 ` [PATCH v3 3/8] udp: Split receive from preparation and send in udp_sock_handler() David Gibson
2023-01-04 5:44 ` [PATCH v3 4/8] udp: Don't handle tap receive batch size calculation within a #define David Gibson
2023-01-04 5:44 ` [PATCH v3 5/8] udp: Pre-populate msg_names with local address David Gibson
2023-01-04 5:44 ` [PATCH v3 6/8] udp: Unify udp_sock_handler_splice() with udp_sock_handler() David Gibson
2023-01-04 17:44 ` Stefano Brivio
2023-01-05 4:25 ` David Gibson [this message]
2023-01-04 5:44 ` [PATCH v3 7/8] udp: Decide whether to "splice" per datagram rather than per socket David Gibson
2023-01-04 5:44 ` [PATCH v3 8/8] udp: Don't use separate sockets to listen for spliced packets 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=Y7ZROA3iNvum7WSk@yekko \
--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).