[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070223115152.GA2565@elte.hu>
Date: Fri, 23 Feb 2007 12:51:52 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Evgeniy Polyakov <johnpol@....mipt.ru>
Cc: Ulrich Drepper <drepper@...hat.com>, linux-kernel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@....com.au>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Zach Brown <zach.brown@...cle.com>,
"David S. Miller" <davem@...emloft.net>,
Suparna Bhattacharya <suparna@...ibm.com>,
Davide Libenzi <davidel@...ilserver.org>,
Jens Axboe <jens.axboe@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
* Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> [...] Those 20k blocked requests were created in about 20 seconds, so
> roughly saying we have 1k of thread creation/freeing per second - do
> we want this?
i'm not sure why you mention thread creation and freeing. The
syslet/threadlet code reuses already created async threads, and that is
visible all around in both the kernel-space and in the user-space
syslet/threadlet code.
While Linux creates+destroys threads pretty damn fast (in about 10-15
usecs - which is roughly the cost of getting a single 1-byte packet
through a TCP socket from one process to another, on localhost), still
we dont want to create and destroy a thread per request.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists