From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M6niA-0007tW-WD
	for qemu-devel@nongnu.org; Wed, 20 May 2009 11:28:07 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M6ni6-0007sf-6i
	for qemu-devel@nongnu.org; Wed, 20 May 2009 11:28:06 -0400
Received: from [199.232.76.173] (port=52391 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M6ni6-0007sT-3V
	for qemu-devel@nongnu.org; Wed, 20 May 2009 11:28:02 -0400
Received: from mail2.shareable.org ([80.68.89.115]:56001)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1M6ni5-0007BW-QM
	for qemu-devel@nongnu.org; Wed, 20 May 2009 11:28:01 -0400
Date: Wed, 20 May 2009 16:27:59 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [PATCH] fix gdbstub support for multiple threads
	in usermode
Message-ID: <20090520152759.GB27666@shareable.org>
References: <1242156943-27850-1-git-send-email-froydnj@codesourcery.com>
	<4A09E1C2.9020302@web.de> <20090519150636.GA23911@codesourcery.com>
	<4A12E418.4040403@web.de> <20090519180110.GE23911@codesourcery.com>
	<4A13A590.8040301@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A13A590.8040301@web.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org

Jan Kiszka wrote:
> 1. Stick head in sand - we will never see so many threads in reality, so
>    neither wrap-around nor performance matters.
> 
> 2. Go for a bitmap-based search of the next free ID (reducing the ID
>    space so that the bitmap has a reasonable size)
> 
> But I have no clue if and how long option 1 will suffice as I have no
> idea how many long-running highly dynamic multi-threaded use cases there
> are or will be for qemu user mode. But if you find option 2 easy enough
> to implement, I would do this nevertheless.

Big web servers can realistically have 1000+ running threads.  But
realistically I don't see anyone running those in QEMU for a while :-)

Creating and destroying large numbers of threads during program
execution is mouch more common, though.

-- Jamie