[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070223121751.GA6626@elte.hu>
Date: Fri, 23 Feb 2007 13:17:51 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Michael K. Edwards" <medwards.linux@...il.com>
Cc: Evgeniy Polyakov <johnpol@....mipt.ru>,
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
* Michael K. Edwards <medwards.linux@...il.com> wrote:
> On 2/22/07, Ingo Molnar <mingo@...e.hu> wrote:
> > maybe it will, maybe it wont. Lets try? There is no true difference
> > between having a 'request structure' that represents the current
> > state of the HTTP connection plus a statemachine that moves that
> > request between various queues, and a 'kernel stack' that goes in
> > and out of runnable state and carries its processing state in its
> > stack - other than the amount of RAM they take. (the kernel stack is
> > 4K at a minimum - so with a million outstanding requests they would
> > use up 4 GB of RAM. With 20k outstanding requests it's 80 MB of RAM
> > - that's acceptable.)
>
> This is a fundamental misconception. [...]
> The scheduler, on the other hand, has to blow and reload all of the
> hidden state associated with force-loading the PC and wherever your
> architecture keeps its TLS (maybe not the whole TLB, but not nothing,
> either). [...]
please read up a bit more about how the Linux scheduler works. Maybe
even read the code if in doubt? In any case, please direct kernel newbie
questions to http://kernelnewbies.org/, not linux-kernel@...r.kernel.org.
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