From owner-p4-projects  Wed Mar 20  7:40:51 2002
Delivered-To: p4-projects@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 7E22937B404; Wed, 20 Mar 2002 07:40:43 -0800 (PST)
Delivered-To: perforce@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id 3EA1037B405
	for <perforce@freebsd.org>; Wed, 20 Mar 2002 07:40:42 -0800 (PST)
Received: (from perforce@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g2KFegE85239
	for perforce@freebsd.org; Wed, 20 Mar 2002 07:40:42 -0800 (PST)
	(envelope-from bb+lists.freebsd.perforce@cyrus.watson.org)
Date: Wed, 20 Mar 2002 07:40:42 -0800 (PST)
Message-Id: <200203201540.g2KFegE85239@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: perforce set sender to bb+lists.freebsd.perforce@cyrus.watson.org using -f
From: Robert Watson <rwatson@FreeBSD.org>
Subject: PERFORCE change 8054 for review
To: Perforce Change Reviews <perforce@freebsd.org>
Sender: owner-p4-projects@FreeBSD.ORG
Precedence: bulk
List-ID: <p4-projects.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20p4-projects>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20p4-projects>
X-Loop: FreeBSD.ORG

http://people.freebsd.org/~peter/p4db/chv.cgi?CH=8054

Change 8054 by rwatson@rwatson_tislabs on 2002/03/20 07:40:05

	Replace my first pass at taskqueue description with a detailed
	one provided by arr.

Affected files ...

... //depot/projects/smpng/sys/design/article.sgml#17 edit

Differences ...

==== //depot/projects/smpng/sys/design/article.sgml#17 (text+ko) ====

@@ -23,7 +23,7 @@
       </author>
     </authorgroup>
 
-    <pubdate>$SMPng: //depot/projects/smpng/sys/design/article.sgml#16 $</pubdate>
+    <pubdate>$SMPng: //depot/projects/smpng/sys/design/article.sgml#17 $</pubdate>
 
     <copyright>
       <year>2002</year>
@@ -546,14 +546,18 @@
     <sect2>
       <title>Taskqueue</title>
 
-      <para>The taskqueue's locking strategy is simple.  There is a mutex,
-	<varname>taskqueue_queues_mutex</varname>, that covers the
-	<varname>taskqueue_queues</varname> TAILQ.  Also there is mutex in
-	the <structname>struct taskqueue</structname> data structure, which
-	is used to protect the elements of the structure.</para>
-
-      <para>- Need to add mutex name, talk about shared vs. exclusive
-	access and use of the mutex.  Is it a leaf mutex?</para>
+       <para> The taskqueue's interface has two basic locks associated
+	with it in order to protect the related shared data.  The
+	<varname>taskqueue_queues_mutex</varname> is meant to serve as a
+	lock to protect the <varname>taskqueue_queues</varname> TAILQ.
+	The other mutex lock associated with this system is the one in the
+	<structname>struct taskqueue</structname> data structure.  The
+	use of the synchronization primitive here is to protect the
+	integrity of the data in the <structname>struct
+	taskqueue</structname>.  It should be noted that there are no
+	separate macros to assist the user in locking down his/her own work
+	since these locks are most likely not going to be used outside of
+	<filename>subr_taskqueue.c</filename>.</para>
     </sect2>
 
     <sect2>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe p4-projects" in the body of the message