Hi,
<[EMAIL PROTECTED]> writes:
>> > Especially the project list needs work. Some of the project
>> > descriptions are only skeletons; I lack the knowledge to fill in the
>> > details. But I know that some of you have much better understanding
>> > about some of these projects.
>>
>> I noticed `
Hello,
[EMAIL PROTECTED], le Tue 11 Mar 2008 04:53:45 +0100, a écrit :
> [I] suggested a more adaptive approach: Keep track of the existing
> threads, and if none of them makes progress in a certain amount of
> time (say 100 ms), allow creating some more threads. But that was
> never implemented.
Olaf,
> The real solution here of course is to fix the thread model
I fully agree that given Mach's architecture, one kernel thread per
extant RPC is the wrong approach.
> using some kind of continuation mechanism: Have a limited number of
> threads (ideally one per CPU) handle incoming requests
Hi,
On Sun, Mar 09, 2008 at 10:17:05PM -0400, Thomas Bushnell BSG wrote:
> On Mon, 2008-03-10 at 01:19 +, Samuel Thibault wrote:
> > This thread is syncing everything, i.e. asking a lot of writes,
> > which triggers the creation of a lot of threads. Unfortunately the
> > superblock was paged
Hi,
On Sun, Mar 09, 2008 at 11:43:12PM +0100, Carl Fredrik Hammar wrote:
> <[EMAIL PROTECTED]> writes:
> > Especially the project list needs work. Some of the project
> > descriptions are only skeletons; I lack the knowledge to fill in the
> > details. But I know that some of you have much better
