I would encourage you *not* to use this function, at this time. The
current design is inadequate, and doesn't actually get used. A
different implementation for use by Crossbow will be provided.
(Yes, this is one of the [good] reasons that GLDv3 is still not public.)
-- Garrett
On Thu, 2007-09-06 at 16:43 -0400, Andrew Gallatin wrote:
> I'm porting a GLDv2 driver to v3, and I'm a bit confused
> about the mac_blank_t function (and the resources stuff
> in general):
>
> typedef void (*mac_blank_t)(void *, time_t, uint_t);
>
> My device can adjust the coalescing time to some number of
> microseconds, but it cannot delay interrupts until after a number of
> frames have arrived. From what I have seen, it looks like some
> drivers (e1000g) ignore the time_t, and just use the count. So is it
> correct to assume that ignoring the count and just using the ticks is
> OK?
>
> Also, the name "ticks" used by some existing drivers implies that the
> value is in clock ticks, and should be converted to microseconds (or
> whatever a particular NIC needs) via something like drv_hztousec. But
> there appear to be some existing drivers like bge that just use the
> value with no conversion. What should I do?
>
> Lastly, what context is this called in? Is it serialized by anything?
> How often is it called?
>
> Thanks,
>
> Drew
> _______________________________________________
> networking-discuss mailing list
> [email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
