From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] IPSEC-SECGW - type no-offload huge latency
Date: Thu, 25 Jan 2018 14:47:56 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA36101595B37@FRAEML521-MBX.china.huawei.com> (raw)
I see that the delay is derived from the MAX_PKT_BURST
If I decrease it, the delay decreases accordingly. And we always transmit a burst of pkts (==MAX_PKT_BURST)
But this behavior is wrong because we should transmit if there are ant pkts ready for tx.
I suspect that the delay is in the ipsec_dequeue logic ...
Any idea ?
Best Regards
Avi
> -----Original Message-----
> From: Avi Cohen (A)
> Sent: Tuesday, 23 January, 2018 5:25 PM
> To: 'users@dpdk.org'
> Subject: IPSEC-SECGW - type no-oofload huge latency
>
> Hi
> I'm running ipsec-secgw with type no-offload (default mode) Clear text pkts
> (ping) are recived , encrypted and send to the end tunnel , then it is decrypted
> and send to the other port at the peer.
> So everything looks OK - except that I get huge latency of 10s of seconds.
> Btw - this application in mode inline-crypto - is working perfect Any idea why is
> the latency ?
> Best Regards
> Avi
reply other threads:[~2018-01-25 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B84047ECBD981D4B93EAE5A6245AA36101595B37@FRAEML521-MBX.china.huawei.com \
--to=avi.cohen@huawei.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).