On Fri, Aug 27, 2004 at 01:05:32PM -0700, Brooks Davis wrote:
> I'd like to proposed adding a new variable, ifi_epoch, to struct
> if_data. It will be set to the time the counters were zeroed,
> currently, the time if_attach was called. The intent is to provide a
> correct value for RFC2233's ifC
Roman Kurakin wrote:
>
> Andre Oppermann:
>
> >Brooks Davis wrote:
> >
> >
> >>I'd like to proposed adding a new variable, ifi_epoch, to struct
> >>if_data. It will be set to the time the counters were zeroed,
> >>currently, the time if_attach was called. The intent is to provide a
> >>correct
Andre Oppermann:
Brooks Davis wrote:
I'd like to proposed adding a new variable, ifi_epoch, to struct
if_data. It will be set to the time the counters were zeroed,
currently, the time if_attach was called. The intent is to provide a
correct value for RFC2233's ifCounterDiscontinuityTime and to
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
__
Brooks Davis wrote:
>
> I'd like to proposed adding a new variable, ifi_epoch, to struct
> if_data. It will be set to the time the counters were zeroed,
> currently, the time if_attach was called. The intent is to provide a
> correct value for RFC2233's ifCounterDiscontinuityTime and to make it
I'd like to proposed adding a new variable, ifi_epoch, to struct
if_data. It will be set to the time the counters were zeroed,
currently, the time if_attach was called. The intent is to provide a
correct value for RFC2233's ifCounterDiscontinuityTime and to make it
easier for applications to veri
