To prevent an infinite loop, threads looking for events inside
kqueue_scan(), insert a `marker' in the list. Such markers are
not accounted and they are removed from the list as soon as the
thread is finished or goes to sleep.
Diff below is a small cleanup to keep the accounting of events in
sync
On Mon, Oct 09, 2017 at 12:15:46PM +0200, Martin Pieuchot wrote:
> Diff below is a small cleanup to keep the accounting of events in
> sync with the number of events on the list. This is a noop for the
> moment, but it's small & easy part to review of my upcoming diff.
Well, not counting the mark
On 09/10/17(Mon) 12:22, Joerg Sonnenberger wrote:
> On Mon, Oct 09, 2017 at 12:15:46PM +0200, Martin Pieuchot wrote:
> > Diff below is a small cleanup to keep the accounting of events in
> > sync with the number of events on the list. This is a noop for the
> > moment, but it's small & easy part t
On Mon, Oct 09, 2017 at 12:27:50PM +0200, Martin Pieuchot wrote:
> On 09/10/17(Mon) 12:22, Joerg Sonnenberger wrote:
> > On Mon, Oct 09, 2017 at 12:15:46PM +0200, Martin Pieuchot wrote:
> > > Diff below is a small cleanup to keep the accounting of events in
> > > sync with the number of events on t
On 09/10/17(Mon) 14:35, Joerg Sonnenberger wrote:
> On Mon, Oct 09, 2017 at 12:27:50PM +0200, Martin Pieuchot wrote:
> > On 09/10/17(Mon) 12:22, Joerg Sonnenberger wrote:
> > > On Mon, Oct 09, 2017 at 12:15:46PM +0200, Martin Pieuchot wrote:
> > > > Diff below is a small cleanup to keep the account
On Mon, Oct 09, 2017 at 12:15:46PM +0200, Martin Pieuchot wrote:
> To prevent an infinite loop, threads looking for events inside
> kqueue_scan(), insert a `marker' in the list. Such markers are
> not accounted and they are removed from the list as soon as the
> thread is finished or goes to sleep