<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#c7">Comment # 7</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:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>(In reply to Karel Rericha from <a href="show_bug.cgi?id=1127#c6">comment #6</a>)
<span class="quote">> Patch didnt help Pablo. Listing this small set each second from patched box:
>
> testbox ~ # nft list set filter private
> table ip filter {
> set private {
> type ipv4_addr
> flags interval
> elements = { 10.0.0.0/8, 100.64.0.0/10, 172.16.0.0/12,
> 192.168.0.0/16}
> }
> }
>
> testbox ~ # watch -n 1 nft list set filter private > /dev/null</span >
I guess you don't hit this problem if you just use non-interval sets.
The good solution is to provide a replacement for the interval set
implementation that we have now, which doesn't scale up as you're noticing.
I can workaround this by providing a lockless path to list. Still if you have
dynamic insertions on that interval tree, you would hit problems.
So the definitive solution is to provide a replacement implementation for
interval sets.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>