Hi Martin,
Martin Blumenstingl wrote on Thu,
18 Apr 2019 21:44:05 +0200:
> Hi Liang,
>
> On Mon, Apr 15, 2019 at 8:04 AM Liang Yang wrote:
> >
> >
> > On 2019/4/12 6:00, Martin Blumenstingl wrote:
> > > Documentation/scheduler/completion.txt states:
> > >Calling init_completion() on the
Hi Martin,
On 2019/4/19 3:44, Martin Blumenstingl wrote:
Hi Liang,
On Mon, Apr 15, 2019 at 8:04 AM Liang Yang wrote:
On 2019/4/12 6:00, Martin Blumenstingl wrote:
Documentation/scheduler/completion.txt states:
Calling init_completion() on the same completion object twice is
most
Hi Liang,
On Mon, Apr 15, 2019 at 8:04 AM Liang Yang wrote:
>
>
> On 2019/4/12 6:00, Martin Blumenstingl wrote:
> > Documentation/scheduler/completion.txt states:
> >Calling init_completion() on the same completion object twice is
> >most likely a bug as it re-initializes the queue to an
On 2019/4/12 6:00, Martin Blumenstingl wrote:
Documentation/scheduler/completion.txt states:
Calling init_completion() on the same completion object twice is
most likely a bug as it re-initializes the queue to an empty queue and
enqueued tasks could get "lost" - use
Documentation/scheduler/completion.txt states:
Calling init_completion() on the same completion object twice is
most likely a bug as it re-initializes the queue to an empty queue and
enqueued tasks could get "lost" - use reinit_completion() in that case,
but be aware of other races.
5 matches
Mail list logo