<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - running nft command creates lag for forwarded packets"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1127#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - running nft command creates lag for forwarded packets"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1127">bug 1127</a>
from <span class="vcard"><a class="email" href="mailto:karel@unitednetworks.cz" title="Karel Rericha <karel@unitednetworks.cz>"> <span class="fn">Karel Rericha</span></a>
</span></b>
<pre>Second result: Zhang your patch DID help. When listing small set like in
previous test there were no visible latency problems now. And when listing big
"known attackers" set there were latency spikes around 15ms. I have waited
until actual traffic was 1.2Gbps so both tests are more or less the same.
Summary: Getting rid of interval sets obviously solves "big sets with interval
flag latency problem" for good :) But when big sets with interval flag are
needed Zhang's patch improves situation a lot: Listing of small sets have no
more latency impacts and listing of big sets with interval raises latency
several times less than previous code.
Pablo, Zhang, thanks for your help.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>