From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: yocto-patches@lists.yoctoproject.org
Subject: [pseudo][PATCH 0/2] RFC: Fix/Add a fast path (async) IPC for ops
Date: Tue, 10 Nov 2026 22:28:05 -0600 [thread overview]
Message-ID: <1794371287-31540-1-git-send-email-mark.hatle@kernel.crashing.org> (raw)
In the distant past a 'FASTOP' was implemented, but never actually worked
properly.
It was observed that a true fast op could be implemented using an async
calling mechanism, however this is implemented differently from the original
work. The new work splits IPC channel into two parts. Then the async calls
are handled as they can be, or forced before the next sync call. This
ensures that all database operations are kept in sync.
Note, this work is on a separate branch as it needs a lot more review
before I would feel safe integrating it. It's also not required to fix
any bugs, but simply should help with performance.
See the async-ipc branch of pseudo repository.
Mark Hatle (2):
Send client requests over one shared datagram socket
Replace FASTOP with requests that don't wait for a reply
README.security | 4 +-
doc/overview | 6 +-
doc/program_flow | 11 ++
doc/pseudo_ipc | 73 ++++++++++++--
enums/msg_type.in | 2 +-
enums/op.in | 50 +++++-----
ports/common/guts/_Exit.c | 16 +++
ports/common/guts/_exit.c | 16 +++
ports/common/guts/execv.c | 4 +
ports/common/guts/execve.c | 4 +
ports/common/guts/execveat.c | 4 +
ports/common/guts/execvp.c | 4 +
ports/common/guts/execvpe.c | 4 +
ports/common/guts/fexecve.c | 4 +
ports/common/pseudo_wrappers.c | 34 +++++++
ports/common/wrapfuncs.in | 2 +
pseudo.1 | 23 ++++-
pseudo.c | 2 +-
pseudo.h | 1 +
pseudo_client.c | 222 +++++++++++++++++++++++++++++++----------
pseudo_client.h | 2 +
pseudo_ipc.c | 42 ++++++++
pseudo_ipc.h | 8 ++
pseudo_server.c | 186 +++++++++++++++++++++++++++++-----
pseudo_util.c | 1 +
pseudo_wrappers.c | 43 ++++++++
test/test-async-abort.c | 44 ++++++++
test/test-async-abort.sh | 40 ++++++++
test/test-async-order.c | 188 ++++++++++++++++++++++++++++++++++
test/test-async-order.sh | 23 +++++
30 files changed, 946 insertions(+), 117 deletions(-)
create mode 100644 ports/common/guts/_Exit.c
create mode 100644 ports/common/guts/_exit.c
create mode 100644 test/test-async-abort.c
create mode 100755 test/test-async-abort.sh
create mode 100644 test/test-async-order.c
create mode 100755 test/test-async-order.sh
--
1.8.3.1
next reply other threads:[~2026-11-11 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 4:28 Mark Hatle [this message]
2026-11-11 4:28 ` [pseudo][PATCH 1/2] Send client requests over one shared datagram socket Mark Hatle
2026-11-11 4:28 ` [pseudo][PATCH 2/2] Replace FASTOP with requests that don't wait for a reply Mark Hatle
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=1794371287-31540-1-git-send-email-mark.hatle@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=yocto-patches@lists.yoctoproject.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.