> On 22 Dec 2018, at 12:48, Damjan Marion via Lists.Fd.Io
> wrote:
>
> flowprobe is per-packet IPFIX flow record generator plugin.
To be perfectly correct it generates ipfix records per flow, but can be
configured to consider the length of a flow to be one packet.
Cheers
Ole
> On 22 Dec 2018, at 09:00, david.leitch@gmail.com wrote:
>
> Hi
> What is difference between "plugins/flowprobe" and "vnet/flow"?
> -=-=-=-=-=-=-=-=-=-=-=-
vnet/flow is my attempt to create flow offload infra which supports different
device driver types (i.e. dpdk rte_flow) and
allows
Hi
What is difference between "plugins/flowprobe" and "vnet/flow"?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11760): https://lists.fd.io/g/vpp-dev/message/11760
Mute This Topic: https://lists.fd.io/mt/28792277/21656
Group Owner:
Hi,
NAT code should be rewritten
Matus
From: vpp-dev@lists.fd.io On Behalf Of
david.leitch@gmail.com
Sent: Wednesday, December 19, 2018 4:56 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Worker Thread Dead Lock on NAT44 IPFIX
hi Matus
Thanks for your answer, can you explain more
hi Matus
Thanks for your answer, can you explain more about this issue?
You mean that I should rewrite "nat_ipfix_logging.c" file to works per thread
or "vnet/ipfix-export/flow_report"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#11697):
-dev] Worker Thread Dead Lock on NAT44 IPFIX
hi
Every time I enable ipfix for NAT, the main thread (vpp_main) is going too
slowly, which is very hard to enter any command and also drop rate increase
that all traffic dropped.
but I got worker thread deadlock once after some hours.
Is it a normal
*hi*
*Every time I enable ipfix for NAT, the main thread (vpp_main) is going too
slowly, which is very hard to enter any command and also drop rate increase
that all traffic dropped.*
*but I got worker thread deadlock once after some hours.
* *Is it a normal behavior that Every time I enable
