Re: locking

From: Waldemar Kornewald (Waldemar.Kornewald_at_web.de)
Date: 09/25/04

  • Next message: Matthew Luckie: "Re: [tcpdump-workers] [PATCH] Add ioctl to disable bpf timestamping" 
    Date: Sat, 25 Sep 2004 11:33:36 +0200
To: FreeBSD-net <freebsd-net@freebsd.org>

    Robert Watson wrote:
    > There are some sections of the network stack, such as the KAME IPSEC
    > implementation, parts of IPv6, and some device drivers, which are not yet
    > completely MPSAFE. This may or may not be an issue depending on what
    > your requirements are. If you have any bug fixes or improvements, we
    > would love to hear about them -- right now our locking is fairly
    > coarse-grained but we'll be looking at contention issues over the next few
    > months to see how best to refine our locking strategy.

    We wanted to have fine-grained locking (BeOS/Haiku emphasizes on
    threading very much), but at least having some locking is better than
    our current situation (nearly no locking ;). Our first aim is to get a
    stable modularized netstack, finally. The next steps would be
    fine-grained locking and maybe trying out iovecs instead of mbufs.
    Having IPv4 ready is a good start. IPv6 is not too urgent at the moment.

    Bye,
    Waldemar Kornewald
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Matthew Luckie: "Re: [tcpdump-workers] [PATCH] Add ioctl to disable bpf timestamping"

    Relevant Pages