From owner-freebsd-threads@FreeBSD.ORG  Tue Jul  6 20:30:28 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A167516A4CE
	for <freebsd-threads@freebsd.org>;
	Tue,  6 Jul 2004 20:30:28 +0000 (GMT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3418B43D5C
	for <freebsd-threads@freebsd.org>;
	Tue,  6 Jul 2004 20:30:28 +0000 (GMT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i66KUPqM015699
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 6 Jul 2004 16:30:25 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i66KUJwo017788;
	Tue, 6 Jul 2004 16:30:19 -0400 (EDT)
	(envelope-from gallatin)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16619.3035.165728.569632@grasshopper.cs.duke.edu>
Date: Tue, 6 Jul 2004 16:30:19 -0400 (EDT)
To: Daniel Eischen <eischen@vigrid.com>
In-Reply-To: <Pine.GSO.4.10.10407061619220.10060-100000@pcnet5.pcnet.com>
References: <16619.2082.399880.649617@grasshopper.cs.duke.edu>
	<Pine.GSO.4.10.10407061619220.10060-100000@pcnet5.pcnet.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: Julian Elischer <julian@elischer.org>
cc: freebsd-threads@freebsd.org
Subject: Re: pthread switch  (was Odd KSE panic)
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jul 2004 20:30:28 -0000


Daniel Eischen writes:
 > Note that he is holding the mutex while calling pthread_cond_signal().
 > If we enable preemption in pthread_cond_signal(), then I suspect it
 > would be even worse than without preemption.
 > 
 > I think the only place where it is sane to enable preemption is
 > on pthread_mutex_unlock().

That certainly makes sense to me.  But I don't want to see you
optimize the threads lib just for my app.   I can always put in an
#ifdef FreeBSD
pthread_yield()
#endif

But what I'm still wondering is where the ~3x slowdown (20usec linux
-> ~60usec, libthr) is coming from.  Is this a factor of the context
switch time and ithreads?

I need to move the driver to a fast interrupt and I need to test
SCHED_BSD as well.  I should probably cvs update to get jhb's
scheduling changes.

Drew