On Wed, Jul 18, 2018 at 8:28 PM, Johannes Thumshirn <jthumshirn@xxxxxxx> wrote: > On Wed, Jul 18, 2018 at 08:06:10PM +0800, Ming Lei wrote: >> IMO the problem isn't related with slow or quick device, it is related with >> the system, especially when it cares about power consumption, such as >> mobile phone, or laptop or servers with lots of disks attached. And we know >> it is often to see some fast disks shipped in laptop, such as NVMe, or other >> SSD. > > Yes but you're only taking locally attached devices into account. > This is very likely harmful on sd devices attached to a > SRP/FC/iSCSI/SAS Target in a SAN environment. These can be really fast > and people investing this money are likely to not like additional > performance penalties. Runtime PM provides options for all these kind of cases. If you care performance, just keep the default setting(device is always in active). If you care power consumption, you may run PM utility to switch runtime PM on for the interested devices. Definitely we are working on solutions in which runtime PM code shouldn't introduce extra obvious cost in fast path, so no need to worry about its effect if you never want to use that. > > Furthermore I'd don't know if any array vendors actually implement > START/STOP DISK, etc.. That won't be one issue as I mentioned above. Thanks, Ming Lei
