[Architecture] Proposing a Snap-Backend for Sub-microsecond IPC Channels Body

[KunshrJain]

The Problem
Flow-IPC provides enterprise-grade abstractions but can benefit from a specialized "Zero-Bypass" backend for ultra-low latency scenarios.

The Solution
Implemented a new Snap transport backend:

snap_shm_transport: A backend that natively implements the
Blob_sender
and
Blob_receiver
concepts using Snap v3.0.
Performance: Provides a direct path for zero-copy message exchange that bypasses the kernel's message queue logic.

Benefit
Enables the highest possible performance for Flow-IPC channels on local hosts.

[ygoldfeld]

I do see your PR. It is a bit rough in the sense that it, like, includes generated binary files and so on. I'd like to know more about the substance of what it's doing though. Will surely look.

[KunshrJain]

Hello
Did you check out the new branch with the changes and explanation ?

[ygoldfeld]

Realistically, just from a basic glance, there is no way this can be a mere quick look. A serious time investment is required, and frankly I probably need to speak to you more interactively. There are very basic things to understand; for example the very idea of it, as written, appears to be "let's put stuff in SHM instead of copying it," and this is happening at the lowest layer, with blobs flying around. But, that sounds a lot like Blob_stream_mq_sender/receiver<Bipc_mq_handle>.

I'm afraid, when it comes to merging into the official main project, that conversation will have to wait, until there is more time from one of us (such as me). Sorry about that.