[DGD] Why use callouts in klib to increment resources?

[Raymond Jennings]

Any concerns about causing a DoS by evading a "tick usage" quota?  The
tick updates don't update this resource (and thus trigger a new
rlimits check) immediately.
On Sun, Oct 21, 2018 at 5:15 AM Felix A. Croes <felix at dworkin.nl> wrote:
>
> Raymond Jennings <shentino at gmail.com> wrote:
>
> > Hey Felix, I was just wondering:
> >
> > Why were increments to decayed resources (including tick updates)
> > handled in a callout and not immediately?
>
> I've been posting about this recently.  Resource counters are shared
> between tasks, and modifying them directly from the task would prevent
> other tasks that access the same resource from running concurrently.
>
>
> > I'm asking because I'm making heavy usage of call_limited and it's
> > building up so many incr_ticks callouts in the rsrc objects that it's
> > throwing errors about running out of callouts.
>
> Increase the size of the callout table.
>
> Regards,
> Felix Croes
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd