On Tue, Feb 23, 2021 at 4:35 PM Gaëtan Rivet wrote:
>
> On Tue, Feb 23, 2021, at 22:56, William Tu wrote:
> > On Wed, Feb 17, 2021 at 8:34 AM Gaetan Rivet wrote:
> > >
> > > When ct_sweep() is far behind on its work, the 'next_wake' returned can
> > > be before the moment it started. When it
On Tue, Feb 23, 2021, at 22:56, William Tu wrote:
> On Wed, Feb 17, 2021 at 8:34 AM Gaetan Rivet wrote:
> >
> > When ct_sweep() is far behind on its work, the 'next_wake' returned can
> > be before the moment it started. When it happens, the thread schedules a
> > zero ms timer that is logged as
On Wed, Feb 17, 2021 at 8:34 AM Gaetan Rivet wrote:
>
> When ct_sweep() is far behind on its work, the 'next_wake' returned can
> be before the moment it started. When it happens, the thread schedules a
> zero ms timer that is logged as an error.
>
> Instead, mark the thread for immediate wake in
When ct_sweep() is far behind on its work, the 'next_wake' returned can
be before the moment it started. When it happens, the thread schedules a
zero ms timer that is logged as an error.
Instead, mark the thread for immediate wake in the next poll_block().
Signed-off-by: Gaetan Rivet
