/ 详情

在grub.cfg文件设置IO调度策略不生效

已挂起
Bug
Opened this issue  
2020-10-29 17:24
  • 操作系统:openEuler 20.03 (LTS) ARM架构
  • 在/etc/default/grub文件中增加io调度策略:elevator=mq-deadline
  • 使用grub2-mkconfig命令更新/boot/grub2/grub.cfg和/boot/efi/EFI/openEuler/grub.cfg文件
  • 重启,查看调度策略并未设置为mq-deadline
    输入图片说明

输入图片说明

  • 另,uos在/etc/default/grub文件中增加io调度策略:elevator=deadline是可以实现的
Attachments

Comments (7)

field created缺陷
field set related repository to openEuler/kernel
展开全部操作日志

Hey Odland, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot .
That means the developers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/sig-infrastructure/command.md to find the details.

field changed description
Alex_Chao set assignee to XieXiuQi
Alex_Chao changed assignee from XieXiuQi to Alex_Chao
Alex_Chao assigned collaborator XieXiuQi

/lib/udev/rules.d/60-block-scheduler.rules里面指定了bfq,把启动参数的配置覆盖了,启动参数想生效的话,删掉/lib/udev/rules.d/60-block-scheduler.rules里面的bfq就好

/lib/udev/rules.d/60-block-scheduler.rules里面指定了bfq,把启动参数的配置覆盖了,启动参数想生效的话,删掉/lib/udev/rules.d/60-block-scheduler.rules里面的bfq就好

@jpzhang187

:+1:

@jpzhang187 @XieXiuQi /lib/udev/rules.d/60-block-scheduler.rules的调度策略与 内核启动参数冲突的话,是否应该修改为默认不写这个调度策略? 其他系统是如何实现的?

@jpzhang187 @XieXiuQi /lib/udev/rules.d/60-block-scheduler.rules的调度策略与 内核启动参数冲突的话,是否应该修改为默认不写这个调度策略? 其他系统是如何实现的?

@Alex_Chao 当前的systemd源码里面这个文件就是这么写的,已经告知了systemd的开发,看他怎么处理吧

@Alex_Chao 当前的systemd源码里面这个文件就是这么写的,已经告知了systemd的开发,看他怎么处理吧

嗯,看 systemd 的策略吧。

@jpzhang187 @Alex_Chao

YangYingliang changed issue state from 待办的 to 已挂起

Sign in to comment

状态
Assignees
Projects
Milestones
Pull Requests
关联的 Pull Requests 被合并后可能会关闭此 issue
Branches
Planed to start   -   Planed to end
-
Top level
Priority
参与者(6)
5329419 openeuler ci bot 1578984659