All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <phill@thesusis.net>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH v8 04/23] scsi: sd: Differentiate system and runtime start/stop management
Date: Wed, 08 Nov 2023 17:15:52 -0500	[thread overview]
Message-ID: <875y2buc13.fsf@vps.thesusis.net> (raw)
In-Reply-To: <7141dc0d-eb1d-41d4-a608-c1fd569e4325@kernel.org>

Damien Le Moal <dlemoal@kernel.org> writes:

> Your PMP is looking like type (1).

Correct, which is why the performance isn't good when I try to access
both disks at the same time.

>> When I enable runtime pm on the drives and the top level port, then try
>> to access the sleeping drive, I see this:
>
> How can you enable runtime PM on a port ? That does not work...

It works on *something*, I'm not not sure whether it is or is not the
port.  /sys/devices/pciblahblah/ata2/power/control can be enabled, and
then the port will be runtime suspended.  I'm not not sure what that is
compared to /sys/devices/pciblahblah/ata2/ata_port/ata2/power/control,
which can't be set to auto, and is also /sys/class/ata_port/ata2.  I'm
not sure why there are two different things that look like an "ata port".

> They are the first 2 devices connected to the PMP port that exist. These
> correspond to your sdd and sde scsi disks.

Right, but the PMP itself is not suspended.  I think that causes an
attempt to access the PMP while the root port that connects to the PMP
is suspended, so that access obviously fails.

> Are you running the latest code from Linus tree ? There is now a check on the
> power state of a device to avoid useless activate.

I hadn't pulled in some time.  Updating now.


  reply	other threads:[~2023-11-08 22:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c0b086ab-dcd5-4b7b-b931-4d407dd7ad47()kernel!org>
2023-10-12 19:01 ` [PATCH v8 04/23] scsi: sd: Differentiate system and runtime start/stop management Phillip Susi
2023-10-13  0:57   ` Damien Le Moal
2023-10-13 14:36     ` Phillip Susi
2023-10-15 22:09       ` Damien Le Moal
2023-10-21 17:56         ` Phillip Susi
2023-10-23  5:49           ` Damien Le Moal
2023-11-03 18:05             ` Phillip Susi
2023-11-03 23:01               ` Phillip Susi
2023-11-06  2:32                 ` Damien Le Moal
2023-11-07 13:27                   ` Phillip Susi
2023-11-07 21:59                     ` Damien Le Moal
2023-11-08 22:07                       ` Phillip Susi
2023-11-06  3:00               ` Damien Le Moal
2023-11-07 13:45                 ` Phillip Susi
2023-11-07 21:48                   ` Phillip Susi
2023-11-07 23:11                     ` Damien Le Moal
2023-11-08 22:15                       ` Phillip Susi [this message]
2023-11-09 22:09                         ` Phillip Susi
2023-11-09 22:57                           ` Damien Le Moal
2023-11-10 16:41                             ` Phillip Susi
2023-11-10  0:43                           ` Damien Le Moal
2023-11-07 22:13                   ` Damien Le Moal
2023-11-08 22:25                     ` Phillip Susi
2023-09-27 14:18 [PATCH v8 00/23] Fix libata suspend/resume handling and code cleanup Damien Le Moal
2023-09-27 14:18 ` [PATCH v8 04/23] scsi: sd: Differentiate system and runtime start/stop management Damien Le Moal
2023-09-27 19:50   ` Martin K. Petersen
2023-10-10 13:09   ` Phillip Susi
2023-10-10 14:04     ` Damien Le Moal
2023-10-15 16:14   ` Phillip Susi
2023-10-15 22:44     ` Damien Le Moal
2023-10-16 12:39       ` Phillip Susi
2023-10-16 12:55         ` Damien Le Moal
2023-10-17 18:03           ` Phillip Susi
2023-10-17 23:32             ` Damien Le Moal
2023-10-20 19:00               ` Phillip Susi
2023-10-18  6:16             ` Damien Le Moal
2023-10-20 21:23               ` Phillip Susi
2023-10-23  5:51                 ` Damien Le Moal
2023-10-26 21:21                   ` Phillip Susi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875y2buc13.fsf@vps.thesusis.net \
    --to=phill@thesusis.net \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.