From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: wait_event()\ wait_event_interruptible()\ wait_event_interruptible_timeout() and wake_up()
Date: Tue, 06 Aug 2019 07:42:06 -0400 [thread overview]
Message-ID: <6613.1565091726@turing-police> (raw)
In-Reply-To: <CAHhAz+jKjnR9vuixfkejSPXnJdM4VU1fJqvppVKAVwdw7xFSTw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 382 bytes --]
On Tue, 06 Aug 2019 14:15:53 +0530, Muni Sekhar said:
> If they do different things, does the waiting threads wakeup order is
> the same in which they were enqueued (FIFO order)?
You missed the point - if you have (for example) something that's waiting for
mouse I/O and something that's waiting for a network packet, under what
conditions will they be using the same wait event?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-08-06 11:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 17:18 wait_event()\ wait_event_interruptible()\ wait_event_interruptible_timeout() and wake_up() Muni Sekhar
2019-07-29 17:28 ` Greg KH
2019-07-29 18:01 ` Bharath Vedartham
2019-07-29 18:07 ` Muni Sekhar
2019-07-29 18:29 ` Valdis Klētnieks
2019-07-29 18:27 ` Valdis Klētnieks
2019-07-30 1:59 ` Muni Sekhar
2019-08-06 8:45 ` Muni Sekhar
2019-08-06 11:42 ` Valdis Klētnieks [this message]
2019-08-06 12:00 ` Muni Sekhar
2019-08-06 12:26 ` Greg KH
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=6613.1565091726@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=munisekharrms@gmail.com \
/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).