[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[linux-lvm] Re: IO scheduler, queue depth, nr_requests
- From: Andrew Morton <akpm osdl org>
- To: Miquel van Smoorenburg <miquels cistron nl>
- Cc: miquels cistron nl, axboe suse de, linux-lvm sistina com, linux-kernel vger kernel org, thornber redhat com
- Subject: [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- Date: Thu Feb 19 09:08:51 2004
Miquel van Smoorenburg <miquels cistron nl> wrote:
>
> The thing is, the bio's are submitted perfectly sequentially. It's just that
> every so often a request (with just its initial bio) gets stuck for a while.
> Because the bio's after it are merged and sent to the device, it's not
> possible to merge that stuck request later on when it gets unstuck, because
> the other bio's have already left the building so to speak.
Oh. So the raid controller's queue depth is larger than the kernel's. So
everything gets immediately shovelled into the device and the kernel is
left with nothing to merge the little request against.
Shouldn't the controller itself be performing the insertion?
- References:
- [linux-lvm] IO scheduler, queue depth, nr_requests
- From: Miquel van Smoorenburg
- [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- From: Miquel van Smoorenburg
- [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- From: Miquel van Smoorenburg
- [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- [linux-lvm] Re: IO scheduler, queue depth, nr_requests
- From: Miquel van Smoorenburg
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]