Re: [dpdk-dev] [PATCH v6 2/4] examples/ipsec-secgw: add fallback session feature

> > > > Inline processing is limited to a specified subset of traffic. It is > > > > often unable to handle more complicated situations, such as fragmented > > > > traffic. When using inline processing such traffic is dropped. > > > > > > > > Introduce fallback session for inline processing allo

Re: [dpdk-dev] [PATCH v6 2/4] examples/ipsec-secgw: add fallback session feature

Hi Konstantin, > > Hi Akhil, > > > > > > > Inline processing is limited to a specified subset of traffic. It is > > > often unable to handle more complicated situations, such as fragmented > > > traffic. When using inline processing such traffic is dropped. > > > > > > Introduce fallback session

Re: [dpdk-dev] [PATCH v6 2/4] examples/ipsec-secgw: add fallback session feature

Hi Akhil, > > > > Inline processing is limited to a specified subset of traffic. It is > > often unable to handle more complicated situations, such as fragmented > > traffic. When using inline processing such traffic is dropped. > > > > Introduce fallback session for inline processing allowing pro

Re: [dpdk-dev] [PATCH v6 2/4] examples/ipsec-secgw: add fallback session feature

Hi All, > > Inline processing is limited to a specified subset of traffic. It is > often unable to handle more complicated situations, such as fragmented > traffic. When using inline processing such traffic is dropped. > > Introduce fallback session for inline processing allowing processing > pac

[dpdk-dev] [PATCH v6 2/4] examples/ipsec-secgw: add fallback session feature

Inline processing is limited to a specified subset of traffic. It is often unable to handle more complicated situations, such as fragmented traffic. When using inline processing such traffic is dropped. Introduce fallback session for inline processing allowing processing packets that normally woul