RE: protecting netgraph calls from outside of the network context

From: Dmitri Denissov (ddenissov_at_sandvine.com)
Date: 05/21/04

  • Next message: Bruce M Simpson: "Re: ia_netbroadcast" 
    To: 'Julian Elischer' <julian@elischer.org>
Date: Thu, 20 May 2004 18:14:11 -0400

    This is kind of a bridge, connected to ng_ether interface nodes.
    Sometimes it queues received packets and later /on a timer call or a call
    from the user space/
    it re-injects the packets using ng_send_data.

    > From: Julian Elischer [mailto:julian@elischer.org]
    > Sent: Thursday, May 20, 2004 5:34 PM
    >
    >
    > Ha! funny you should ask that exactly now..
    > I was just discussing this with Robert Watson..
    >
    > The answer is "it depends on what you want to do".
    >
    > What DO you want to do and what does your node do?
    > netgraph has internal locking in 5.x that you need to
    > interact with but it should be pretty transparrent
    > depending on what you are doing..
    >
    >
    > On Thu, 20 May 2004, Dmitri Denissov wrote:
    >
    > > Hi,
    > >
    > > Currently netgraph code uses splnet/splx to protect timeout calls.
    > > This doesn't work with 5.2 SMP kernel. What is the proper method
    > > here for a custom netgraph node? Is the Giant lock only the way?
    > >
    > > Thanks
    > >
    > > --
    > > Dmitri
    _______________________________________________
    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: Bruce M Simpson: "Re: ia_netbroadcast"