On Thu, Jun 16 2005, Tejun Heo wrote:
> Hello, Jens.
> Hello, Andrew.
>
> In cfq_find_next_crq(), cfq tries to find the next request by
> choosing one of two requests before and after the current one.
> Currently, when choosing the next request, if there's no next request,
> the next candidate is NULL, resulting in selection of the previous
> request. This results in weird scheduling. Once we reach the end, we
> always seek backward.
>
> The correct behavior is using the first request as the next
> candidate. cfq_choose_req() already has logics for handling wrapped
> requests.
Good spotting, applied. I'll set up an iosched git tree as well, with a
cfq-ts branch.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
