From: Darren Hart <dvhltc@us.ibm.com>
To: ltp-list <ltp-list@lists.sourceforge.net>
Cc: Gowrishankar <gowrishankar.m@in.ibm.com>,
Vernon Mauery <vernux@us.ibm.com>
Subject: [LTP] [PATCH][realtime] prio-wake: allow for optional locking prior to broadcast
Date: Mon, 24 Aug 2009 15:14:22 -0700 [thread overview]
Message-ID: <4A9310BE.8050109@us.ibm.com> (raw)
prio-wake: allow for optional locking prior to broadcast
Allow the user to decide if the mutex should be held prior to
calling pthread_cond_broadcast(). Default remains the same.
Tested with and without the argument as well as with both 0 and 1
passed to the argument. Values other than 0 and 1 will result in locking
the mutex.
Signed-off-by: Darren Hart <dvhltc@us.ibm.com>
Acked-By: Dinakar Guniguntala <dino@in.ibm.com>
Acked-by: Vernon Mauery <vernux@us.ibm.com>
Acked-by: Gowrishankar <gowrishankar.m@in.ibm.com>
---
func/prio-wake/prio-wake.c | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
Index: realtime/func/prio-wake/prio-wake.c
===================================================================
--- realtime.orig/func/prio-wake/prio-wake.c
+++ realtime/func/prio-wake/prio-wake.c
@@ -56,6 +56,7 @@
#include <librttest.h>
volatile int running_threads = 0;
static int rt_threads = 0;
+static int locked_broadcast = 1;
static pthread_cond_t cond = PTHREAD_COND_INITIALIZER;
static pthread_mutex_t mutex;
static volatile nsec_t beginrun;
@@ -67,6 +68,8 @@ void usage(void)
rt_help();
printf("prio-wake specific options:\n");
printf(" -n# #: number of worker threads\n");
+ printf(" -l# 1:lock the mutex before broadcast, 0:don't\n");
+ printf(" defaults to 1\n");
}
int parse_args(int c, char *v)
@@ -80,6 +83,9 @@ int parse_args(int c, char *v)
case 'n':
rt_threads = atoi(v);
break;
+ case 'l':
+ locked_broadcast = atoi(v);
+ break;
default:
handled = 0;
break;
@@ -106,9 +112,11 @@ void *master_thread(void* arg)
printf("%08lld us: Master thread about to wake the workers\n", start/NS_PER_US);
/* start the children threads */
- rc = pthread_mutex_lock(&mutex);
+ if (locked_broadcast)
+ rc = pthread_mutex_lock(&mutex);
rc = pthread_cond_broadcast(&cond);
- rc = pthread_mutex_unlock(&mutex);
+ if (locked_broadcast)
+ rc = pthread_mutex_unlock(&mutex);
while (running_threads > 0)
sleep(1);
@@ -161,7 +169,7 @@ int main(int argc, char* argv[])
int i;
setup();
- rt_init("hn:", parse_args, argc, argv);
+ rt_init("hn:l:", parse_args, argc, argv);
if (rt_threads == 0) {
numcpus = sysconf(_SC_NPROCESSORS_ONLN);
@@ -172,7 +180,9 @@ int main(int argc, char* argv[])
printf("\n-----------------------\n");
printf("Priority Ordered Wakeup\n");
printf("-----------------------\n");
- printf("Worker Threads: %d\n\n", rt_threads);
+ printf("Worker Threads: %d\n", rt_threads);
+ printf("Calling pthread_cond_broadcast() with mutex: %s\n\n",
+ locked_broadcast ? "LOCKED" : "UNLOCKED");
pri_boost = 3;
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-08-24 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 22:14 Darren Hart [this message]
2009-08-25 9:58 ` [LTP] [PATCH][realtime] prio-wake: allow for optional locking prior to broadcast Subrata Modak
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=4A9310BE.8050109@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=gowrishankar.m@in.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vernux@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.