From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: eli@mellanox.co.il
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: wait_for_completion_timeout problem ???
Date: Thu, 1 Mar 2007 16:14:30 +0100 [thread overview]
Message-ID: <b647ffbd0703010714m5f8546ebw95ec607b38ba7e1@mail.gmail.com> (raw)
In-Reply-To: <1172760574.5175.42.camel@mtls03>
On 01/03/07, Eli Cohen <eli@mellanox.co.il> wrote:
> >...
> > wait_for_completion_timeout() should return something different that
> > encodes the fact /event happened/ and not just /event happened _and_ a
> > caller has got scheduled back earlier than timeout.
> That possibility crossed my mind but I ruled it out since the the
> timeout is 10 sec while completion arrived less then 4 msec after
> calling wait_for_completion_timeout(). So it appears to me unlikely that
> it will the task will be in the run list but will not get CPU time for
> nearly 10 seconds. I will give it a try though. I will increase timeout
> to 20 sec.
>
Mea culpa. Don't know why I took it as 10 ms.. Yep, in case of seconds
it rather becomes a mere theoretical possibility.
Are you sure there are no other "waiters" being blocked on the same
"completion" at the same time? complete_all()?
Anyway, do "cat /proc/your_task_pid/status" and look at the "State: "
field. It should be "R" in case wake_up_*() was called for this task.
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2007-03-01 15:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 13:32 Eli Cohen
2007-03-01 14:28 ` Dmitry Adamushko
2007-03-01 14:49 ` Eli Cohen
2007-03-01 15:14 ` Dmitry Adamushko [this message]
2007-03-01 15:39 ` Eli Cohen
2007-03-01 16:05 ` Eli Cohen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b647ffbd0703010714m5f8546ebw95ec607b38ba7e1@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=eli@mellanox.co.il \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome