kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: miloody@gmail.com (loody)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Questions about complete
Date: Thu, 6 Jan 2011 16:05:10 +0800	[thread overview]
Message-ID: <AANLkTimR7PyJS000BsA-Q=pRXXY9Wht6_QtkRowv=OLM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=E7Q9kJvG1KUPv2xS3WK_12byksSrVH_g2UST2@mail.gmail.com>

hi:

2011/1/6 Pavan Savoy <pavan_savoy@sify.com>:
> On Thu, Jan 6, 2011 at 12:23 PM, loody <miloody@gmail.com> wrote:
>> hi:
>>
>> 2011/1/6 Pavan Savoy <pavan_savoy@sify.com>:
>>> On Thu, Jan 6, 2011 at 11:48 AM, loody <miloody@gmail.com> wrote:
>>>>
>>>> Dear all:
>>>> I know complete will wake up the process who call wait_complete.
>>>> Is there any methods I can use to measure how long from calling
>>>> complete to the process that detect done=1?
>>>> Regards,
>>>> miloody
>>>
>>> returned value of wait_for_completion_timeout ?
>> No.
>> I want to measure the duration of complete to the time of wake up
>> process who is pending on wait.
>
> Ah, Ok, Got it...
> I would do a copy of jiffies before the complete and do a diff for
> jiffies after the
> wait_for_ ...
>
> I suppose there would be much more better/optimized way ....
thank U :)
why I ask so is I am porting kernel to other platform right now.
and I found the time of getting complete is too long.
What I mean is
function A call wait_complete_timeout
function B complete
theoretically A will get complete and leave successfully
but my platform A will told me that before timeout the complete is not got.

Regards,
miloody

  reply	other threads:[~2011-01-06  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  6:18 Questions about complete loody
2011-01-06  6:33 ` Pavan Savoy
2011-01-06  6:53   ` loody
2011-01-06  6:56     ` Pavan Savoy
2011-01-06  8:05       ` loody [this message]
2011-01-06  8:51         ` Rajat Sharma
2011-01-07 14:21           ` loody
2011-01-08 10:24             ` Rajat Sharma

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='AANLkTimR7PyJS000BsA-Q=pRXXY9Wht6_QtkRowv=OLM@mail.gmail.com' \
    --to=miloody@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).