public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] [PATCH] prio-wake: avoid glibc to kernel sleep race
Date: Thu, 28 Jan 2010 11:39:35 -0800	[thread overview]
Message-ID: <4B61E7F7.3000502@us.ibm.com> (raw)

prio-wake: avoid glibc to kernel sleep race

In the unlocked broadcast scenario, there exists a race between when the
running_threads variable reaches rt_threads and when the last worker_thread
blocks in the kernel after a cond_wait(). It is possible for a thread to miss
the broadcast if it fails to sleep before the broadcast is issued.  

The previous code did not guarantee a small window of time to allow the threads
to get to sleep.  It also used an unreasonably large sleep time which
unnecessarily extended the length of the test run time.  This patch ensures some
time is given to the threads to get to sleep and at the same time uses a much
shorter (1000x) sleep period which results in a 50-100x reduction in test run
time. Lastly, two unecessary loops waiting for the threads to complete were
removed, relying on pthread_join() instead to wait for the threads to complete.

Signed-off-by: Darren Hart <dvhltc@us.ibm.com>
Acked-by: Will Schmidt <will_schmidt@vnet.ibm.com>

---
 func/prio-wake/prio-wake.c |   10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

Index: realtime/func/prio-wake/prio-wake.c
===================================================================
--- realtime.orig/func/prio-wake/prio-wake.c
+++ realtime/func/prio-wake/prio-wake.c
@@ -108,7 +108,10 @@ void *master_thread(void* arg)
 
 	/* make sure children are started */
 	while (running_threads < rt_threads)
-		sleep(1);
+		usleep(1000);
+	/* give the worker threads a chance to get to sleep in the kernel
+	 * in the unlocked broadcast case. */
+	usleep(1000);
 
 	start = rt_gettime() - beginrun;
 
@@ -120,8 +123,6 @@ void *master_thread(void* arg)
 	if (locked_broadcast)
 		rc = pthread_mutex_unlock(&mutex);
 
-	while (running_threads > 0)
-		sleep(1);
 	return NULL;
 }
 
@@ -157,9 +158,6 @@ void *worker_thread(void* arg)
 
 	rc = pthread_mutex_unlock(&mutex);
 
-	/* wait for all threads to quit */
-	while (running_threads > 0)
-		sleep(1);
 	return NULL;
 }
 
-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2010-01-28 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 19:39 Darren Hart [this message]
2010-04-21 20:23 ` [LTP] [PATCH] prio-wake: avoid glibc to kernel sleep race Darren Hart
2010-04-22  6:09   ` Rishikesh K Rajak

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=4B61E7F7.3000502@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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