5 Replies to “More ipfw work”

  1. The latency / performance for the 99% though gets crazy with ipfw.

    Seems like some type of lock is happening because without ipfw, the 99% is flat. With ipfw, the 99% jumps exponentially high.

  2. For rule based blacklist, the rule iteration is linear, so performance drop w/ increasing # of rules is much expected. Rule list itself is _lockless_, but rule evaluation has its own cost. That’s the main reason to use table for blacklist, which scales pretty well w/ the # of addresses.

  3. Thanks Sepherosa. That was great insight.

    You do awesome work.

    Really wish DragonflyBSD had wider adoption so that more people would get to appreciate all you have accomplished on the network stack.

  4. Maybe add “alias ls ls -G” or Change prompt to Display current path (i.e. “%n@%m:%~ # ” ) for better Out of the Box experience.

  5. I agree with Erik on the work that Sepherosa has done; if you keep an eye on at least the FreeBSD mailing lists, he shows up there too so some of the work is getting elsewhere. As for more people adopting DragonFly, it’s a double edged sword. More people using sometimes is more people complaining.

Leave a Reply

Your email address will not be published.