[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070221230351.GC32031@elte.hu>
Date: Thu, 22 Feb 2007 00:03:51 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Michael K. Edwards" <medwards.linux@...il.com>
Cc: 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>,
Ulrich Drepper <drepper@...hat.com>,
Zach Brown <zach.brown@...cle.com>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
"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
* Michael K. Edwards <medwards.linux@...il.com> wrote:
> 1) Documentation of what you can and can't do safely from a threadlet,
> given that it runs in an unknown thread context;
you can do just about anything from a threadlet, using bog standard
procedural programming. (Certain system-calls are excluded at the moment
out of caution - but i'll probably lift restrictions like sys_clone()
use because sys_clone() can be done safely from a threadlet.)
The code must be thread-safe, because the kernel can move execution to a
new thread anytime and then it will execute in parallel with the main
thread. There's no other requirement.
Wrt. performance, one good model is to run request-alike functionality
from a threadlet, to maximize parallelism.
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