> -Original Message-
> From: Thomas Monjalon
> Sent: Friday, April 10, 2020 6:14 PM
> To: Bill Zhou
> Cc: Matan Azrad ; Ori Kam ;
> wenzhuo...@intel.com; jingjing...@intel.com;
> bernard.iremon...@intel.com; john.mcnam...@intel.com;
> marko.kovace...@intel.com; ferruh.yi...@intel.com;
> a
From: Ori Kam
> > -Original Message-
> > From: BillZhou
> > Sent: Friday, April 10, 2020 12:47 PM
> > To: Matan Azrad ; Bill Zhou
> ;
> > Ori Kam ; wenzhuo...@intel.com;
> > jingjing...@intel.com; bernard.iremon...@intel.com;
> > john.mcnam...@intel.com; marko.kovace...@intel.com; Thomas
> -Original Message-
> From: BillZhou
> Sent: Friday, April 10, 2020 12:47 PM
> To: Matan Azrad ; Bill Zhou ;
> Ori Kam ; wenzhuo...@intel.com;
> jingjing...@intel.com; bernard.iremon...@intel.com;
> john.mcnam...@intel.com; marko.kovace...@intel.com; Thomas Monjalon
> ; ferruh.yi...@in
On Fri, Apr 10, 2020 at 5:38 PM Andrew Rybchenko
wrote:
>
> On 4/10/20 12:46 PM, BillZhou wrote:
> > One of the reasons to destroy a flow is the fact that no packet matches the
> > flow for "timeout" time.
> > For example, when TCP\UDP sessions are suddenly closed.
> >
> > Currently, there is no a
On 4/10/20 12:46 PM, BillZhou wrote:
One of the reasons to destroy a flow is the fact that no packet matches the
flow for "timeout" time.
For example, when TCP\UDP sessions are suddenly closed.
Currently, there is no any DPDK mechanism for flow aging and the
applications use their own ways to de
10/04/2020 11:46, BillZhou:
> One of the reasons to destroy a flow is the fact that no packet matches the
> flow for "timeout" time.
> For example, when TCP\UDP sessions are suddenly closed.
>
> Currently, there is no any DPDK mechanism for flow aging and the
> applications use their own ways to d
6 matches
Mail list logo
