On 3/8/24 15:24, Ilya Maximets wrote:
On 3/7/24 22:29, Ilya Maximets wrote:
On 3/7/24 21:59, Adrian Moreno wrote:
On 3/7/24 17:54, Ilya Maximets wrote:
On 3/7/24 16:18, Adrian Moreno wrote:
** Background ** Currently, OVS supports several packet
sampling mechanisms (sFlow, per-bridge
On 3/7/24 22:29, Ilya Maximets wrote:
> On 3/7/24 21:59, Adrian Moreno wrote:
>>
>>
>> On 3/7/24 17:54, Ilya Maximets wrote:
>>> On 3/7/24 16:18, Adrian Moreno wrote:
** Background ** Currently, OVS supports several packet
sampling mechanisms (sFlow, per-bridge IPFIX, per-flow IPFIX).
On 3/7/24 21:59, Adrian Moreno wrote:
>
>
> On 3/7/24 17:54, Ilya Maximets wrote:
>> On 3/7/24 16:18, Adrian Moreno wrote:
>>> ** Background **
>>> Currently, OVS supports several packet sampling mechanisms (sFlow,
>>> per-bridge IPFIX, per-flow IPFIX). These end up being translated into a
>>>
On 3/7/24 17:54, Ilya Maximets wrote:
On 3/7/24 16:18, Adrian Moreno wrote:
** Background **
Currently, OVS supports several packet sampling mechanisms (sFlow,
per-bridge IPFIX, per-flow IPFIX). These end up being translated into a
userspace action that needs to be handled by ovs-vswitchd's
On 3/7/24 16:18, Adrian Moreno wrote:
> ** Background **
> Currently, OVS supports several packet sampling mechanisms (sFlow,
> per-bridge IPFIX, per-flow IPFIX). These end up being translated into a
> userspace action that needs to be handled by ovs-vswitchd's handler
> threads only to be
** Background **
Currently, OVS supports several packet sampling mechanisms (sFlow,
per-bridge IPFIX, per-flow IPFIX). These end up being translated into a
userspace action that needs to be handled by ovs-vswitchd's handler
threads only to be forwarded to some third party application that
will
