Francois, Almost every VPP feature assumes that data is adjacent to vlib_buffer_t.
It will be huge rework to make this happen, and it will slow down performance as it will introduce dependent read at many places in the code... So to answer your question, we don’t have such plans. Thanks, Damjan > On 4 Oct 2017, at 17:17, Francois Ozog <francois.o...@linaro.org> wrote: > > Hi, > > Hardware that is capable of 50Gbps and above (at 64 byte line rate) > place packets next to each other in large memory zones rather than in > individual memory buffers. > > To handle packets without copy would require vlib_buffer_t to allow > packet data to be NOT consecutive to it. > > Are there plans or have there been discussions on this topic before ? > (I checked the archive and did not found any reference). > > -FF > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
