[DGD] Callout hack

[Shentino]

Wouldn't that wreak havoc with thread concurrency once MP comes around
the block?  I'm leery about centralizing this way...

As far as I know, DGD's statedumps only use a 32 bit word to encode
all callout delays, so even if I could extend it, I'd need a way to
pack the bits back again so that my superlong callouts could persist
across a statedump.  I've done a trial run of eliminating the 60.0
second top limit.  The delays appear to be "unwrapping" in intervals
of 256 seconds, but as long as DGD is running, they still go off at
roughly the same time as a second based callout for the same time.

It just gets all screwy if I dump state.

On 9/1/06, Felix A. Croes <felix at dworkin.nl> wrote:
> Shentino <shentino at gmail.com> wrote:
>
> > What files would I need to change besides call_out.c?
> >
> > Having super long millisecond callouts really appeals to me.
>
> Apart from a limit check in kfun/std.c, all changes should be in the
> file you mentioned.  The rest you will have to do on your own -- I'm
> not going to guide you through it step by step :)
>
> And I still recommend a time server in LPC, instead.  You need that
> anyway if you want some callouts to occur at particular times, rather
> than after a delay.
>
> Regards,
> Dworkin
> __________________________________________
> http://mail.dworkin.nl/mailman/listinfo/dgd
>