Re: [HEADS UP!] IPFW Ideas: possible SoC 2008 candidate




here are some of my ideas for ipfw changes:

1/ redo locking so that packets do not have to get locks on the structure... I have several ideas on this
2/ allow separate firewalls to be used at different parts of the network stack (i.e allow multiple taboe sto co-exist)
3/ possibly keeping per CPU stats..

_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: [DRIVER SUBMISSION] DRBD wants to go mainline
    ... Kthreads disallow all signals by default, as they should, and you really shouldn't need to write any logic to handle or> do-certain-things-on-seeing a signal in a well designed kernel thread. ... When your receiving thread gets data it takes appropriate locks and processes it, then releases the locks and goes back to waiting for packets. ... The pool of IO-generating threads (IE: What would ordinarily be userspace) ...
    (Linux-Kernel)
  • Re: Fire Engine??
    ... If they tested TCP-over-NFS then I'm pretty sure Linux lost badly because ... There are too many locks. ... This means locking and multiple ... lists of packets instead of single packets. ...
    (Linux-Kernel)
  • Re: Threadsafe StringList
    ... lock, Tconference locks and clients leaving and joining calls, connecting ... class would run on it's own thread, with a message queue (as this is ... packets, probably in the form of a memorystream). ... locks the stream and then shoves it packet on the end. ...
    (borland.public.delphi.language.objectpascal)