From owner-freebsd-threads@FreeBSD.ORG  Tue Jul  6 18:26:57 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 0716C16A4CE
	for <freebsd-threads@freebsd.org>;
	Tue,  6 Jul 2004 18:26:57 +0000 (GMT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 887CA43D39
	for <freebsd-threads@freebsd.org>;
	Tue,  6 Jul 2004 18:26:56 +0000 (GMT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i66IQifP015923;
	Tue, 6 Jul 2004 14:26:44 -0400 (EDT)
Date: Tue, 6 Jul 2004 14:26:44 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Andrew Gallatin <gallatin@cs.duke.edu>
In-Reply-To: <16618.52660.343754.933037@grasshopper.cs.duke.edu>
Message-ID: <Pine.GSO.4.10.10407061425570.14885-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 18:26:57 -0000

On Tue, 6 Jul 2004, Andrew Gallatin wrote:

> 
> FWIW, inserting a pthread_yield() just before the ioctl call in the
> worker thread speeds things up quite a bit (100us -> 73us) in
> combination with kern.threads.virtual_cpu=1.

Then I guess preemption and setting thread priorities
accordingly would help your problem...

-- 
Dan Eischen