On Dec 1, 2006, at 11:50 PM, Sumantra Kundu wrote:

> In version 2, the CC algorithm resides inside the IO scheduler. It
> monitors the dynamics of the two queues: read and write; only when it
> thinks that the write queue is being filled at a rate that might
> indicate congestion,  it nails down the process that has initiated
> most of the write request in the queue and puts it to sleep.  That way
> we concern ourselves only with IO bound processes.

Where does it do this, and what mechanism does it use to block  
offending processes?

-- thorpej