public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Cc: Niklas Cassel <cassel@kernel.org>
Subject: Re: [PATCH] scsi: core: Disabe CDL by default
Date: Fri, 7 Jun 2024 08:08:43 +0900	[thread overview]
Message-ID: <7e27dc26-ab23-465f-8cd2-97e635fc37b3@kernel.org> (raw)
In-Reply-To: <03766042-bfa8-44bf-9684-44a912ad2c73@acm.org>

On 6/7/24 00:48, Bart Van Assche wrote:
> On 6/5/24 23:46, Damien Le Moal wrote:
>> For scsi devices supporting the Command Duration Limits feature set, the
>> user can enable/disable this feature use through the sysfs device
>> attribute cdl_enable. This attribute modification triggers a call to
>> scsi_cdl_enable() to enable and disable the feature for ATA devices and
>> set the scsi device cdl_enable to the user provided bool value.
> 
> Do we really need to disable CDL by default? Has it been considered to
> enable CDL by default if the Command Duration Limit mode pages that have
> been defined in SPC-5 are supported?

We cannot do that as that would potentially break users of ATA NCQ priority. The
reason is that for ATA drives that support both NCQ priority and CDL, if CDL is
enabled, NCQ priority cannot be used. If we were to change CDL to be enabled by
default, NCQ priority users would need to disable it before enabling NCQ
priority. That can break existing setups.

And this has been like this since kernel 6.5, so I am not going to change this now.

-- 
Damien Le Moal
Western Digital Research


      reply	other threads:[~2024-06-06 23:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  5:46 [PATCH] scsi: core: Disabe CDL by default Damien Le Moal
2024-06-06  9:32 ` Christoph Hellwig
2024-06-06 12:11   ` Damien Le Moal
2024-06-06 13:23 ` Niklas Cassel
2024-06-06 15:13   ` Niklas Cassel
2024-06-06 23:11   ` Damien Le Moal
2024-06-06 15:48 ` Bart Van Assche
2024-06-06 23:08   ` Damien Le Moal [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=7e27dc26-ab23-465f-8cd2-97e635fc37b3@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=cassel@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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