public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/4] UDP flow socket preliminaries
Date: Tue, 25 Mar 2025 14:00:06 +1100	[thread overview]
Message-ID: <20250325030010.970144-1-david@gibson.dropbear.id.au> (raw)

As discussed on our recent call, I'm working towards using connected
sockets on both sides of UDP flows.  This series makes some
preliminary reworks that simplify things and make that easier.

David Gibson (4):
  udp: Common invocation of udp_sock_errs() for vhost-user and "buf"
    paths
  udp: Simplify checking of epoll event bits
  udp_vu: Factor things out of udp_vu_reply_sock_data() loop
  udp: Share more logic between vu and non-vu reply socket paths

 udp.c          | 120 +++++++++++++++++++++++++------------------------
 udp_internal.h |   2 +-
 udp_vu.c       |  68 +++++++++-------------------
 udp_vu.h       |   9 ++--
 4 files changed, 88 insertions(+), 111 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-03-25  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25  3:00 David Gibson [this message]
2025-03-25  3:00 ` [PATCH 1/4] udp: Common invocation of udp_sock_errs() for vhost-user and "buf" paths David Gibson
2025-03-25  3:00 ` [PATCH 2/4] udp: Simplify checking of epoll event bits David Gibson
2025-03-25  3:00 ` [PATCH 3/4] udp_vu: Factor things out of udp_vu_reply_sock_data() loop David Gibson
2025-03-25  3:00 ` [PATCH 4/4] udp: Share more logic between vu and non-vu reply socket paths 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=20250325030010.970144-1-david@gibson.dropbear.id.au \
    --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).