public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org, Niklas Cassel <cassel@kernel.org>,
	Igor Pylypiv <ipylypiv@google.com>,
	Xingui Yang <yangxingui@huawei.com>,
	John Garry <john.g.garry@oracle.com>
Subject: Re: [PATCH v5 0/2] Prevent non-NCQ command starvation
Date: Sun, 04 Jan 2026 16:49:09 -0500	[thread overview]
Message-ID: <yq1fr8lt5g1.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260104082203.1212962-1-dlemoal@kernel.org> (Damien Le Moal's message of "Sun, 4 Jan 2026 17:22:01 +0900")


Damien,

> This small patch series addresses potential command starvation issues
> with non-NCQ commands issued to a device accessed through a
> multi-queue libsas HBA. In such setup, a non-NCQ command issued to a
> device may suffer long delays and even complete starvation if the
> device is under a constant workload of NCQ commands issued from
> multiple queues.

LGTM.

Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>

-- 
Martin K. Petersen

      parent reply	other threads:[~2026-01-04 21:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-04  8:22 [PATCH v5 0/2] Prevent non-NCQ command starvation Damien Le Moal
2026-01-04  8:22 ` [PATCH v5 1/2] ata: libata-scsi: refactor ata_scsi_translate() Damien Le Moal
2026-01-04 17:05   ` Niklas Cassel
2026-01-05 10:30   ` John Garry
2026-01-05 23:26   ` Igor Pylypiv
2026-01-04  8:22 ` [PATCH v5 2/2] ata: libata-scsi: avoid Non-NCQ command starvation Damien Le Moal
2026-01-04 17:16   ` Niklas Cassel
2026-01-05 10:51   ` John Garry
2026-01-06 21:03   ` Igor Pylypiv
2026-01-14  3:16   ` yangxingui
2026-01-04 21:49 ` Martin K. Petersen [this message]

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=yq1fr8lt5g1.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=ipylypiv@google.com \
    --cc=john.g.garry@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=yangxingui@huawei.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox