patchless server kernel
(LU-20)
|
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | Lustre 2.5.0 |
| Type: | Technical task | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | Prakash Surya (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | patch | ||
| Rank (Obsolete): | 5855 |
| Description |
|
If we are moving to a patchless server kernel, Lustre will need to automatically set the block device scheduler to "deadline" if it is currently set to "cfq", since the "cfq" scheduler exhibits very poor performance for high-bandwidth applications like Lustre. We shouldn't override the setting if "noop" is set by the administrator. Currently this is done via the kernel config file setting CONFIG_DEFAULT_DEADLINE=y in our config files, but this will not be possible if we are not building our own kernels (the upstream default is "cfq", which is more suitable for desktop use). This should probably be done via mount_utils_ldiskfs.c for ldiskfs devices (since the device name is specified on the command-line). This is more difficult for ZFS devices, since there is not a simple mapping from the mounted "device" and the underlying disks. I suspect it should be done internal to the "zfs" utility (or in the kernel) itself, when the device is first being imported. |
| Comments |
| Comment by Prakash Surya (Inactive) [ 18/Dec/12 ] |
|
Please see: http://review.whamcloud.com/4853 Currently it does not make an exception for the "noop" scheduler, and will try to override any currently set scheduler with "deadline". |
| Comment by Peter Jones [ 21/Jun/13 ] |
|
This patch appears to have landed to master. Can the ticket be marked as resolved or does some further work still remain? |
| Comment by Prakash Surya (Inactive) [ 21/Jun/13 ] |
|
Patch landed, |
[LU-2498]