On Wed, Oct 17, 2018 at 07:48:33AM -0700, Bart Van Assche wrote: > On 10/17/18 3:05 AM, Jan Kara wrote: > > Well, the problem with this is that big distro people really don't care > > much because they already use udev for tuning the IO scheduler. So whatever > > defaults the kernel is going to pick likely won't be seen by distro > > customers. Embedded people seem to be driving this effort because they > > either don't run udev or they feel not all their teams building new > > products have enough expertise to come up with a proper set of rules... > What's missing in this discussion is a definition of "embedded system". Is > that a system like a streaming player for TV channels that neither has a > keyboard nor a display or a system that can run multiple apps simultaneously > like a smartphone? I think the difference matters because some embedded > devices hardly do any background I/O nor load any executable code from > storage after boot. So at least for some embedded devices the problem > discussed in this e-mail thread does not exist. It's a combination of things - smartphones are definitely part of the target audience but other things can be affected, I'd guess your streaming TV player example can have issues if it's got local storage and downloads things in the background for example. There's definitely systems that never really use storage once they're booted but there's also things that move data around and/or have interactive apps. Even with some of the things that don't really use storage at runtime it can be important to help cut down boot times.
Attachment:
signature.asc
Description: PGP signature
