Memory management in a seastar application is a very important topic, as seastar applications are usually long running server applications that want to maximize the usage of memory as well as be resilient to memory fragmentation.
Add a section on this to the docs/tutorial.md based on the lessons we learned at ScyllaDB. In a nutshell: when large buffers are needed prefer storing data in a chunke

Hi all,
What is the agreement for contributions?

It seems that I didn't find the inbound agreement.
In general, the inbound license should be 'Developer Certificate of Origin, version 1.1'.
The outbound license should be 'Apache License 2.0'
And the legal information of inbound license should be in CONTRIBUTING.md.

My boss want to know the inbound license of this project and the link.

As the title say.

As per: https://groups.google.com/forum/#!topic/trex-tgn/_Owo86jrieU

I've noticed that throughout documentation for stateful TRex manual, and many of the supplied traffic profiles, have this acronym "SFR" used.

doc example: https://trex-tgn.cisco.com/trex/doc/trex_manual.html#_traffic_profiles_provided_with_the_trex_package
traffic profile mix example: https://github.com/cisco-system-traff

lagopus.conf must be under //etc/lagopus/ and not /etc/lagopus/.
Note: is prefix set by --prefix option.

Maybe we should update QUICKSTART.md ?

Current on Lagopus0.1.2:

    150      % sudo cp lagopus/samples/lagopus.conf /etc/lagopus/
    151      % sudo vi /etc/lagopus/lagopus.conf

Should be

    % sudo cp lagopus/samples/lagopus.conf /<prefix>/etc/lagopus/
    % 

Can Gatekeeper compete with leading DDoS protections like Voxility and OVH SAS?

I doubt but I have to ask because I am jumping into server hosting :D

Service chains can be a great way to test a great deal of complex functionality in the openNetVM system. The idea is for a program to be written (probably in /examples) that allows for .json configuration file for running different chains of NFs pooled together. We are envisioning a python program that can parse JSON data to start circular or linear chain functionality with different example N

Background

Currently, we can read Ethernet frames with VLAN-tags, but not generate/create ones. We'd like to be able to generate packets with VLAN-tagged Ethernet frames. More information about tags can be found at https://docs.rs/capsule/latest/capsule/packets/struct.Ethernet.html#8021q and https://docs.rs/capsule/latest/capsule/packets/struct.Ethernet.html#8021ad, including links to specs/

This is an optimization to reduce the time it takes to build/deploy YAStack.

Compilation of YAStack can be optimized by pre-compiling source code that does not depend on DPDK. This can help build the image faster since now only DPDK and dependent code will have to be compiled.

CI could have differents stages to:

• run style
• run tests
• build documentation

with stages, tests will be runned in parallel and CI should be faster to check commits.

see the travis documentation about stages.