<div dir="ltr">Any further thoughts on this?<div><br></div><div>--Saied</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 11, 2016 at 4:19 PM, Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Mar 11, 2016 at 04:11:50PM -0800, Saied Kazemi wrote:<br>
> Good question. A machine that I was testing on had a few hundred entries<br>
> which made it look like criu was hung. With the -n it's obviously a LOT<br>
> faster but it'd be best to use a command that would load the modules much<br>
> more quickly. This is not an area that I've had much experience.<br>
<br>
</span>I guess we could modprobe. I think we dropped the modprobe from the<br>
_diag modules because there was an easy netlink way to get the modules<br>
to load which didn't cost us an exec. since we're doing an exec here<br>
anyway to run the iptables binaries, modprobe might be simpler.<br>
<br>
The other option is to figure out some netlink way to specify an<br>
invalid rule. I'm not sure what that would look like off the top of my<br>
head, though :)<br>
<span class="HOEnZb"><font color="#888888"><br>
Tycho<br>
</font></span></blockquote></div><br></div>