Hi Anoob,
On 3/21/2018 10:50 AM, Anoob Joseph wrote:
Hi Akhil,
If you are fine with the existing code, I'll send a revised patchset
incorporating the comment change you had suggested for 3rd patch. Shall
I proceed?
Thanks,
Anoob
Yes you can send the patchset with existing code.
BTW we ar
Hi Akhil,
If you are fine with the existing code, I'll send a revised patchset
incorporating the comment change you had suggested for 3rd patch. Shall
I proceed?
Thanks,
Anoob
On 14/03/18 11:36, Anoob Joseph wrote:
Hi Akhil,
Please see inline.
Thanks,
Anoob
On 13/03/18 17:54, Akhil Goyal
Hi Akhil,
Please see inline.
Thanks,
Anoob
On 13/03/18 17:54, Akhil Goyal wrote:
Hi Anoob,
On 3/1/2018 2:51 PM, Anoob Joseph wrote:
For inline protocol processing, the PMD/device is required to maintain
the ESN. But the application is required to monitor ESN overflow to
initiate SA expiry.
Hi Anoob,
On 3/1/2018 2:51 PM, Anoob Joseph wrote:
For inline protocol processing, the PMD/device is required to maintain
the ESN. But the application is required to monitor ESN overflow to
initiate SA expiry.
For such cases, application would set the ESN soft limit. An IPsec event
would be rai
For inline protocol processing, the PMD/device is required to maintain
the ESN. But the application is required to monitor ESN overflow to
initiate SA expiry.
For such cases, application would set the ESN soft limit. An IPsec event
would be raised by rte_eth_event framework, when ESN hits the soft
5 matches
Mail list logo