Re: Updating callout_reset

From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 01/26/04

  • Next message: Mike Silbersack: "Re: Updating callout_reset" 
    To: Mike Silbersack <silby@silby.com>
Date: Mon, 26 Jan 2004 07:34:27 +0100

    In message <20040125230314.S730@odysseus.silby.com>, Mike Silbersack writes:

    >In order to ensure that modules and the like do not break, I would like to
    >propose that we leave callout_reset defined as is and create a new
    >function, callout_set (or some other clever name) which takes a struct
    >*timespec in place of ticks.

    No, not timespec.

    Timespecs are stupid, slow, clumsy and unhandy and cumbersome.

    With a timespec you either need an MPunsafe hack function like
    libevents evConsTime() or a local stack variable.

    Make it a 64bit count of nanoseconds instead that way it can be
    used as a literal constant.

    It's OK with me if we want to have a function to contain the "*
    1000000000LL" factor for us, and maybe even convenience functions
    for milli and microseconds. 

    -- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: Mike Silbersack: "Re: Updating callout_reset"