<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Atomically updating/reloading a large set with nft -f is excessively slow"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1439#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Atomically updating/reloading a large set with nft -f is excessively slow"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1439">bug 1439</a>
from <span class="vcard"><a class="email" href="mailto:public_timo.s@silentcreek.de" title="Timo Sigurdsson <public_timo.s@silentcreek.de>"> <span class="fn">Timo Sigurdsson</span></a>
</span></b>
<pre>(In reply to kfm from <a href="show_bug.cgi?id=1439#c3">comment #3</a>)
<span class="quote">> This seems to be a duplicate of <a class="bz_bug_link
bz_status_NEW "
title="NEW - nft stalls on EAGAIN upon repeatedly flushing and populating a set"
href="show_bug.cgi?id=1392">bug 1392</a>, for which I still haven't
> discerned any operational workaround.</span >
Indeed, this seems to be the same issue. I missed that one.
<span class="quote">> My view is that some serious thought should be given to supporting ipsets.
> As you have noticed, the present implementation of native sets suffers from
> various bugs and, though it pains me to say it, it just isn't stable enough
> to usurp ipsets at the current time.</span >
Yeah, I also checked whether it's possible to match ipsets with nftables, but
concluded that wasn't the case as I couldn't find any information on it...</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>