diff options
| author |   Deepak S <deepak.s@linux.intel.com> | 2017-11-21 17:44:20 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@opnfv.org> | 2017-11-21 17:44:20 +0000 |
| commit | 84e41af60682783dd193037cd35a3c66d39a5941 (patch) | |
| tree | f4d191834eb7c067eaeed87ef018332d812c7e0e /docs/submodules/container4nfv | |
| parent | 5f17d988cf4aaae7705848834718bbf171e81654 (diff) | |
Update git submodules
* Update docs/submodules/samplevnf from branch 'master'
- Merge "Add support for nop mode with l3 submode"
- Add support for nop mode with l3 submode
The l3 submode was not supported in nop mode, as the nop mode uses some
specific nop thread (and not generic). When L3 is specified, the nop mode
must use the generic thread. In addition the l3 submode is implemented
differently than other submodes. It is not supported through task_init
structures (i.e. each task does not have to explicitely tell that it
supports l3 submode). But this prevented to run both a nop with no submode
and a nop with a l3 submode. Note that nop with l3 is usually not very useful
- it handles arp (requests and response) but as nop, it does not swap IP
addresses. So with a real switch, the packets transmitted will be received
back... and l3 mode is usually mainly usefull when using a switch.
However, there is at least one nop mode where l3 submode makes sense:
when the nop does not transmit. In such cases, for instace used in
conjunction with a gen l3, the nop receives all packets and forward
the arp requests and responses to the master for handling.
Change-Id: I992121db285ba25a11cbb494092a6afc6fe55a58
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
Diffstat (limited to 'docs/submodules/container4nfv')
0 files changed, 0 insertions, 0 deletions