-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/20/2013 09:48 AM, Phillip Susi wrote:
My original idea was actually to just have the system resume force
the runtime pm status to suspended, then it will take care of
calling the runtime resume which can easily start the drive, but I
was
On 13-11-18 10:54 AM, Phillip Susi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2013 8:06 PM, Phillip Susi wrote:
I don't see anything particularly inefficient about issuing the
command in the eh path ( in fact, libata always uses the eh path to
handle power management ).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2013 9:23 AM, Mark Lord wrote:
Yeah, solve that, and you're golden. I totally understand the
motivation for this patch, and would love to have it working on my
machines here too.
But it may have to be some kind of sysfs optional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2013 8:06 PM, Phillip Susi wrote:
I don't see anything particularly inefficient about issuing the
command in the eh path ( in fact, libata always uses the eh path to
handle power management ). You can of course, use the
manage_start_stop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/17/2013 01:43 AM, James Bottomley wrote:
OK, so three people have now told you that's not how the code
works. Why don't you just read it? because there's not really much
point us reading your patches until you do.
I have, which is why I
On 13-11-17 11:15 AM, Phillip Susi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/17/2013 01:43 AM, James Bottomley wrote:
OK, so three people have now told you that's not how the code
works. Why don't you just read it? because there's not really much
point us reading your
On Sun, 2013-11-17 at 11:15 -0500, Phillip Susi wrote:
On 11/17/2013 01:43 AM, James Bottomley wrote:
OK, so three people have now told you that's not how the code
works. Why don't you just read it? because there's not really much
point us reading your patches until you do.
I have,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/17/2013 06:54 PM, Douglas Gilbert wrote:
Even if the SCSI EH code does spin-up the disk, it is inefficient
and undesirable to send a device into EH for what is a normal,
predictable situation (i.e. that a SCSI disk will need a START STOP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/17/2013 07:09 PM, James Bottomley wrote:
Because you don't damn well listen. Two emails ago I said:
The error handler is not automatically activated for a not
ready/initializing command required because of multi-path
And I replied that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/16/2013 12:23 AM, Mark Lord wrote:
Ditto for many SATA disks with power up in standby enabled.
Ditto for my previous response; the kernel ( in this case the libata
layer ) notices this and takes care of starting it. The third patch I
posted
On Thu, 2013-11-07 at 16:16 -0500, Phillip Susi wrote:
On 11/7/2013 1:21 PM, Douglas Gilbert wrote:
On 13-11-06 08:57 PM, Phillip Susi wrote:
Don't bother forcing disks to spin up on resume, as they will do
so automatically when accessed, and forcing them to spin up slows
down the resume.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/16/2013 01:20 PM, James Bottomley wrote:
No disk does, neither SCSI nor ATA. The error handler is not
automatically activated for a not ready/initializing command
required because of multi-path. We override the default behaviour
via
On Sat, 2013-11-16 at 22:50 -0500, Phillip Susi wrote:
On 11/16/2013 01:20 PM, James Bottomley wrote:
No disk does, neither SCSI nor ATA. The error handler is not
automatically activated for a not ready/initializing command
required because of multi-path. We override the default
On 13-11-07 01:21 PM, Douglas Gilbert wrote:
On 13-11-06 08:57 PM, Phillip Susi wrote:
Don't bother forcing disks to spin up on resume, as they
will do so automatically when accessed, and forcing them
to spin up slows down the resume. Add a second bit to the
manage_start_stop flag to restore
On 13-11-06 08:57 PM, Phillip Susi wrote:
Don't bother forcing disks to spin up on resume, as they
will do so automatically when accessed, and forcing them
to spin up slows down the resume. Add a second bit to the
manage_start_stop flag to restore the previous behavior.
SCSI disks when in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/7/2013 1:21 PM, Douglas Gilbert wrote:
On 13-11-06 08:57 PM, Phillip Susi wrote:
Don't bother forcing disks to spin up on resume, as they will do
so automatically when accessed, and forcing them to spin up slows
down the resume. Add a
16 matches
Mail list logo
