Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
correctly configure I/O Scheduler for usage with the YAML file
We had recently a bug with the I/O Scheduler where it was not configured correctly for the case where --max-io-requests (legacy) was passed. The solution for that involved testing for whether or not we have specified a capacity for the io_queue: an io_queue with a capacity is a legacy io_queue, and an io_queue without a capacity is configured with the new yaml method. The problem is that despite that being the intention, that was not what I wrote. Instead of testing for _capacity to be the default, I tested for cfg.capacity, which is divided by the number of I/O Queues already As a result, we would now never take the yaml-config branch. This patch changes that and also proactively works to avoid such problems in the future by changing the default state to optional, instead of just std::numeric_limits<unsigned>::max(). Signed-off-by: Glauber Costa <[email protected]> Message-Id: <[email protected]>
- Loading branch information