[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Thread model

From: olafBuddenhagen
Subject: Re: Thread model
Date: Sun, 16 Mar 2008 08:21:19 +0100
User-agent: Mutt/1.5.17+20080114 (2008-01-14)


On Wed, Mar 12, 2008 at 05:12:03PM +0100, Marcus Brinkmann wrote:

> As for the threading model, more than one kernel thread per real CPU
> doesn't seem to make much sense in most cases.

Well, add a "per processing step" to make this statement more generally
true. In some cases, it's useful to have a distinct set of worker
threads for each processing step, working in a assemly line like fashion
each thread picks a request from one wait queue, does it's work, and
pushes it to the next wait queue.

This model specifically should improve performance for servers that are
constantly busy, processing many requests in parallel; and under the
condition that the amount of data touched in the processing is
relatively small compared to the amount of code.

It also simplifies control flow and locking. Certain optimisations
become obvious.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]