doc: description packet's road in butterfly#387
doc: description packet's road in butterfly#387outscale-toa wants to merge 1 commit intooutscale:developfrom
Conversation
|
Hi, few general comments about documentation:
And particularly to this PR: what about this title: |
outscale-toa
force-pushed
the
description
branch
3 times, most recently
from
78e7c85 to
fccf269
Compare
|
s/packet's/packets/ |
doc/DESCRIPTION.md
Outdated
|
|
||
| ### Poll | ||
|
|
||
| - We collect packets and its numbers in ethernet device queue, store them in array. |
There was a problem hiding this comment.
Traduction:
on collecte les paquets et son nombre dans la queue du périphérique ethernet, les stock dans tableau.
doc/DESCRIPTION.md
Outdated
| ### Poll | ||
|
|
||
| - We collect packets and its numbers in ethernet device queue, store them in array. | ||
| - We rebuild all metadata for each packet and burst all packets in opposite direction |
There was a problem hiding this comment.
We rebuild packets metadata.
Burst them.
doc/DESCRIPTION.md
Outdated
| ### Burst | ||
|
|
||
| - We collect packets, its numbers, put them in ethernet device queue. | ||
| - We burst packets in the queue on ethernet port and free memory. |
There was a problem hiding this comment.
put them in ethernet device queue.
We burst packets in the queue so it's not the same operation ?
free memory Which one ?
Signed-off-by: Thiery Ouattara <thiery.ouattara@outscale.com>
outscale-toa
force-pushed
the
description
branch
from
fccf269 to
28091bb
Compare
|
Also, s/Packet road/packet flow/ |
| @@ -0,0 +1,88 @@ | |||
| DESCRIPTION | |||
|
|
||
| ### Poll: | ||
|
|
||
| - We collect VM packets in the queue. If not packet in the queue it return. |
There was a problem hiding this comment.
s/not/no/
s/in/are in/
| ## Packets go to VM (VHOST) | ||
|
|
||
| ### Burst: | ||
| - Vhost bricks got all packet |
There was a problem hiding this comment.
I'm not sure of that ^
I mean each brick "got all packets"
| @@ -0,0 +1,88 @@ | |||
| DESCRIPTION | |||
|
|
|||
There was a problem hiding this comment.
I might add some schema here:
scenario 1: VM to VM in the same VNI on the same host
/----[Firewall ?]--[Antispoof]--[ sniffer ?]--[vhost, tap or bench brick]
[switch]<
\----[Firewall ?]--[Antispoof]--[ sniffer ?]--[vhost, tap or bench brick]
There was a problem hiding this comment.
I'll do other schema latter
There was a problem hiding this comment.
scenario 2: VM to VM in the same VNI on diferent host with one VN of the same VNI par host
/- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
{The WEB} <
\- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
There was a problem hiding this comment.
scenario 3: VM to VM in the same VNI on diferent host with more than 1 VN of the same VNI on 1rst host
/- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
/- [nic] -- [sniffer ?] -- [vtep] -- [switch] {- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
{The WEB} <
\- [nic] -- [sniffer ?] -- [vtep] -- [firewall?] -- [antispoof] -- [sniffer ?] -- [vhost, tap or bench brick]
3 participants
Signed-off-by: Thiery Ouattara thiery.ouattara@outscale.com