Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Thu, Sep 22, 2016 at 6:26 PM, Rafael J. Wysocki wrote: > On 9/16/2016 5:26 PM, Andy Lutomirski wrote: >> >> I'm adding power management to the nvme driver, and I'm exposing >> exactly one knob via sysfs: the maximum permissible latency. This >> isn't a power domain

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Thu, Sep 22, 2016 at 6:26 PM, Rafael J. Wysocki wrote: > On 9/16/2016 5:26 PM, Andy Lutomirski wrote: >> >> I'm adding power management to the nvme driver, and I'm exposing >> exactly one knob via sysfs: the maximum permissible latency. This >> isn't a power domain issue, and it has no

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On 9/16/2016 5:26 PM, Andy Lutomirski wrote: I'm adding power management to the nvme driver, and I'm exposing exactly one knob via sysfs: the maximum permissible latency. This isn't a power domain issue, and it has no dependencies -- it's literally just the maximum latency that the driver may

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On 9/16/2016 5:26 PM, Andy Lutomirski wrote: I'm adding power management to the nvme driver, and I'm exposing exactly one knob via sysfs: the maximum permissible latency. This isn't a power domain issue, and it has no dependencies -- it's literally just the maximum latency that the driver may

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Fri, Sep 16, 2016 at 8:54 AM, One Thousand Gnomes wrote: > On Fri, 16 Sep 2016 08:26:03 -0700 > Andy Lutomirski wrote: > >> I'm adding power management to the nvme driver, and I'm exposing >> exactly one knob via sysfs: the maximum permissible

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Fri, Sep 16, 2016 at 8:54 AM, One Thousand Gnomes wrote: > On Fri, 16 Sep 2016 08:26:03 -0700 > Andy Lutomirski wrote: > >> I'm adding power management to the nvme driver, and I'm exposing >> exactly one knob via sysfs: the maximum permissible latency. This >> isn't a power domain issue, and

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Fri, 16 Sep 2016 08:26:03 -0700 Andy Lutomirski wrote: > I'm adding power management to the nvme driver, and I'm exposing > exactly one knob via sysfs: the maximum permissible latency. This > isn't a power domain issue, and it has no dependencies -- it's > literally just the

Re: Should drivers like nvme let userspace control their latency via dev_pm_qos?

On Fri, 16 Sep 2016 08:26:03 -0700 Andy Lutomirski wrote: > I'm adding power management to the nvme driver, and I'm exposing > exactly one knob via sysfs: the maximum permissible latency. This > isn't a power domain issue, and it has no dependencies -- it's > literally just the maximum latency

Should drivers like nvme let userspace control their latency via dev_pm_qos?

I'm adding power management to the nvme driver, and I'm exposing exactly one knob via sysfs: the maximum permissible latency. This isn't a power domain issue, and it has no dependencies -- it's literally just the maximum latency that the driver may impose on I/O for power saving purposes. ISTM

Should drivers like nvme let userspace control their latency via dev_pm_qos?

I'm adding power management to the nvme driver, and I'm exposing exactly one knob via sysfs: the maximum permissible latency. This isn't a power domain issue, and it has no dependencies -- it's literally just the maximum latency that the driver may impose on I/O for power saving purposes. ISTM