cfq-iosched: reset oom_cfqq in cfq_set_request()
authorVivek Goyal <vgoyal@redhat.com>
Thu, 9 Jul 2009 20:13:16 +0000 (22:13 +0200)
committerJens Axboe <axboe@carl.(none)>
Fri, 10 Jul 2009 18:31:54 +0000 (20:31 +0200)
In case memory is scarce, we now default to oom_cfqq. Once memory is
available again, we should allocate a new cfqq and stop using oom_cfqq for
a particular io context.

Once a new request comes in, check if we are using oom_cfqq, and if yes,
try to allocate a new cfqq.

Tested the patch by forcing the use of oom_cfqq and upon next request thread
realized that it was using oom_cfqq and it allocated a new cfqq.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>

No differences found