Jérôme Jutteau

We just have to check that link connection / disconnection should not break anything

We should use vhost's private data to store our brick.

It's a dpdk's vhost limitation: we cannot bust more that 32 packets. Maybe we should try to make 2x burst or fix the problem in vhost implementation.

For the moment, DPDK's vhost only support server mode for vhost-user. Client mode will appear soon, permitting packetgraph application to attach to already running VM.

Commit 9c69b0fe556983b67861a692603ee58e6d08a39e introduce a communication bug with butterfly. Going to revert the commit, add test and repair this later

DPDK now offers txprep to well prepare packets to be sent on an interface.

http://nanomsg.org/ The idea would be to encapsulate received packet and send it to a nanomsg endpoint. We can possibly embed some packets metadata.

We may have to start a qemu in order to have a vhost-user client

This issue pop after having a memory issue in [this](https://github.com/outscale/packetgraph/pull/317) pull request. We may have to add test with a lot of edges or maybe the problem is just related...