Re: I/O schedulers for m68k

On Sat, 2014-07-12 at 12:13 +1000, Finn Thain wrote: On Fri, 11 Jul 2014, Ben Hutchings wrote: I noticed that the default I/O scheduler on m68k is noop, which is really bad for spinning rust. This is because the default must be built-in, and you put these overrides in the m68k config:

I/O schedulers for m68k

I noticed that the default I/O scheduler on m68k is noop, which is really bad for spinning rust. This is because the default must be built-in, and you put these overrides in the m68k config: CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=m I think this is a mistake and that cfq should be reverted

Re: I/O schedulers for m68k

Ben Hutchings dixit: I think this is a mistake and that cfq should be reverted to built-in so it can be the default, as on other architectures. Any objection to me doing that? None from me, I was probably just saving space pre-initrd. Which one is chosen, I will leave up to the experts, i.e.

Re: I/O schedulers for m68k

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/11/2014 05:15 PM, Ben Hutchings wrote: I think this is a mistake and that cfq should be reverted to built-in so it can be the default, as on other architectures. Any objection to me doing that? If that means a speed up in the end, I'm all

Re: I/O schedulers for m68k

On Fri, 2014-07-11 at 15:32 +, Thorsten Glaser wrote: Ben Hutchings dixit: I think this is a mistake and that cfq should be reverted to built-in so it can be the default, as on other architectures. Any objection to me doing that? None from me, I was probably just saving space

Re: I/O schedulers for m68k

On Fri, 11 Jul 2014, Ben Hutchings wrote: I noticed that the default I/O scheduler on m68k is noop, which is really bad for spinning rust. This is because the default must be built-in, and you put these overrides in the m68k config: CONFIG_IOSCHED_DEADLINE=m CONFIG_IOSCHED_CFQ=m I