packetgraph
packetgraph copied to clipboard
Packetgraph library is a collection of network bricks you can connect to form a network graph.
In a lot of burst function, we use a #ifndef PG_BENCH_... with the same code. We can clean this and have a unique #define.
When we receive a signal pg_stop(void); is not call, but the hugepages and bricks metafiles are still in the filesystem. We need to find a better was to handle this...
[pipsecd](https://svnweb.freebsd.org/ports/head/net/pipsecd/) ? [strongswan](https://www.strongswan.org/) ?
The idea is to implement a websocket brick (client or server) based on standard [rfc6455](https://tools.ietf.org/html/rfc6455). Here, the brick just take a packet from packetgraph, encapsulate it in a websocket message...
That's a lot in a issue title but it's just to keep the idea: Stopping a graph, change a little thing, restart the graph may have a big cost as...
Implement an AoE server to provide disks over the network. We would be able to flow AoE packets through packetgraph and build other bricks using AoE protocol as a backend...