From: Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com>
To: anish singh <anish198519851985@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: how long wait_for_completion_interruptible_timeout() blocks
Date: Thu, 20 Jun 2019 12:58:16 +0530 [thread overview]
Message-ID: <CAPY=qRTXpsDFitnBuPt3rxWjqhMW+DehC38yhVbJZWNAW3em_w@mail.gmail.com> (raw)
In-Reply-To: <CAK7N6vpFv57PXFmeq1eroS7iN04Nqv-djY35j-AS-ZCToiG6Qw@mail.gmail.com>
On Thu, Jun 20, 2019 at 11:38 AM anish singh
<anish198519851985@gmail.com> wrote:
>
>
>
> On Wed, Jun 19, 2019 at 10:47 PM Subhashini Rao Beerisetty <subhashbeerisetty@gmail.com> wrote:
>>
>> Hi All,
>>
>> I’ve two Linux systems, I tried to measure how long
>> wait_for_completion_interruptible_timeout() blocked after completion
>> is signaled by complete() call. I noticed two different results in
>> both systems.
>>
>> In one system I noticed this duration in between 10 to 60 micro
>> seconds, where as in other system it is in between 20 to 500 micro
>> seconds. I’d like to know what factors can affect this latency? Also,
>> is there any solution to reduce this latency?
>
>
> This is a problem which is fixed by RT Linux patches.
Can these patches be applied to Linux kernel source? If so can you
please give more information on this... where to find these patches?
> It is taking time as Linux is not RTOS and scheduler took time to put your task in running state which is expected and depends on many factors: such as load, interrupts and so on.
>>
>>
>>
>>
>> Thanks,
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies@kernelnewbies.org
>> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-06-20 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 17:16 how long wait_for_completion_interruptible_timeout() blocks Subhashini Rao Beerisetty
2019-06-20 6:07 ` anish singh
2019-06-20 7:28 ` Subhashini Rao Beerisetty [this message]
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='CAPY=qRTXpsDFitnBuPt3rxWjqhMW+DehC38yhVbJZWNAW3em_w@mail.gmail.com' \
--to=subhashbeerisetty@gmail.com \
--cc=anish198519851985@gmail.com \
--cc=kernelnewbies@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).