From owner-acpi-jp@jp.freebsd.org  Thu Dec  6 04:13:09 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id EAA67055;
	Thu, 6 Dec 2001 04:13:09 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id EAA67049;
	Thu, 6 Dec 2001 04:13:07 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (root@localhost [127.0.0.1])
	(authenticated as iwa with CRAM-MD5)
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id fB5JD5P77215;
	Thu, 6 Dec 2001 04:13:05 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Date: Thu, 06 Dec 2001 04:13:01 +0900 (JST)
Message-Id: <20011206.041301.60918133.iwasaki@jp.FreeBSD.org>
To: acpi-jp@jp.freebsd.org, msmith@freebsd.org
Cc: iwasaki@jp.FreeBSD.org
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
In-Reply-To: <200112051814.fB5IEeJ01089@mass.dis.org>
References: <20011205.170201.112206601.iwasaki@jp.FreeBSD.org>
	<200112051814.fB5IEeJ01089@mass.dis.org>
X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1521
Subject: [acpi-jp 1521] Re: Call for testers: Semaphore and Thread
 implementaion 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

$B$$$o$5$-$G$9(B

From: Mike Smith <msmith@freebsd.org>
Subject: [acpi-jp 1520] Re: Call for testers: Semaphore and Thread implementaion 
Date: Wed, 05 Dec 2001 10:14:40 -0800
Message-ID: <200112051814.fB5IEeJ01089@mass.dis.org>

> > Hi,
> > I've created paches for Semaphore and Thread implementaion and
> > some tunings of ACPI components in order to improve AML Mutex handling.
> > 
> > http://people.freebsd.org/~iwasaki/acpi/acpi-mutex-20011204.diff
> > # Note that this includes acpica patch posted in my previous mail.
> > 
> > Please review & test it and let me know if any problems.  I'm planning
> > to commit this (maybe 1 week later) and make this enabled as default.
> 
> Argh.  I still think that enabling threading in the interpreter is a Bad 
> Idea.  Unless you can convince me that Microsoft does this by default, I 
> would rather make it a tunable option.  
> 
> Writing threaded code that works properly is difficult; I'd hazard a 
> guess to say that it's completely beyond your average ASL programmer. 8(

My concern about current implementation is that task queue kernel
thread is shared with some other drivers and we cannot estimate how long
does it take to complete the interpreter execution.  I'm sure that
very long interpreter execution by task queue thread affect other
drivers tasks, they will be delayed even when interpreter is sleeping.
We'd better to complete each tasks quickly ASAP, I think.
I think having dedicated thread for interpreter and giving chance to
execute tasks for other drivers is not so bad idea.
Single thread for interpreter would be enough in most cases.

Thanks
