From: Jamie Lokier <jamie@shareable.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] fix gdbstub support for multiple threads in usermode
Date: Wed, 20 May 2009 16:27:59 +0100 [thread overview]
Message-ID: <20090520152759.GB27666@shareable.org> (raw)
In-Reply-To: <4A13A590.8040301@web.de>
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
prev parent reply other threads:[~2009-05-20 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 19:35 [Qemu-devel] [PATCH] fix gdbstub support for multiple threads in usermode Nathan Froyd
2009-05-12 20:53 ` [Qemu-devel] " Jan Kiszka
2009-05-13 5:08 ` vibisreenivasan
2009-05-13 14:13 ` vibisreenivasan
2009-05-19 14:59 ` Nathan Froyd
2009-05-21 8:19 ` vibi sreenivasan
2009-05-19 15:06 ` Nathan Froyd
2009-05-19 16:53 ` Jan Kiszka
2009-05-19 18:01 ` Nathan Froyd
2009-05-20 6:39 ` Jan Kiszka
2009-05-20 15:27 ` Jamie Lokier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090520152759.GB27666@shareable.org \
--to=jamie@shareable.org \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).