Re: proposed new if_data variable

From: Charles Swiger (cswiger_at_mac.com)
Date: 08/27/04

  • Next message: Roman Kurakin: "Re: proposed new if_data variable"
    Date: Fri, 27 Aug 2004 17:09:32 -0400
    To: Brooks Davis <brooks@one-eyed-alien.net>
    
    

    On Aug 27, 2004, at 4:05 PM, Brooks Davis wrote:
    > Since this will increase the size of struct if_data and thus struct
    > ifnet, the change needs to be made now if it's going to be made for
    > 5-STABLE. Any comments on this idea?

    I think the change is useful, by all means.

    -- 
    -Chuck
    _______________________________________________
    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: Roman Kurakin: "Re: proposed new if_data variable"

    Relevant Pages

    • Re: if_data size issues
      ... Brooks Davis wrote: ... >>Given the pain this change is causing and the limited impact of ... theory that I can use a time_t without changing the struct size. ... I think it would be useful to declare upfront that should a ...
      (freebsd-arch)
    • Re: if_data size issues
      ... Brooks Davis wrote: ... > theory that I can use a time_t without changing the struct size. ... >>to declare any specific timetables right now. ... reasonable position to take. ...
      (freebsd-arch)
    • Re: if_data size issues
      ... Brooks Davis wrote: ... > theory that I can use a time_t without changing the struct size. ... I think it would be useful to declare upfront that should a ... conversion, as very few people will be doing it... ...
      (freebsd-arch)
    • proposed new if_data variable
      ... It will be set to the time the counters were zeroed, ... Since this will increase the size of struct if_data and thus struct ... the change needs to be made now if it's going to be made for ... From: Brooks Davis ...
      (freebsd-net)
    • Re: Allocating AF constants for vendors.
      ... Its relationship cardinality w.r.t struct ifnet is 1:1 - for each ifnet, there is a router_info - but only if AF_INET is attached to that ifnet. ... These are worked around by constantly checking if a struct is allocated or deallocated upon any reference to them. ... We would also be tying ourselves down to the notion of a vendor in any AF_ allocation. ...
      (freebsd-net)