[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7b3b29ee-8e2d-476b-8edd-290c3f00dc85@acm.org>
Date: Tue, 8 Oct 2024 10:38:51 -0700
From: Bart Van Assche <bvanassche@....org>
To: ed.tsai@...iatek.com, peter.wang@...iatek.com,
Alim Akhtar <alim.akhtar@...sung.com>, Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Stanley Jhu <chu.stanley@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: wsd_upstream@...iatek.com, chun-hung.wu@...iatek.com,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] scsi: ufs: ufs-mediatek: configure individual LU queue
flags
On 10/7/24 11:59 PM, ed.tsai@...iatek.com wrote:
> +static void ufs_mtk_config_scsi_dev(struct scsi_device *sdev)
> +{
> + struct ufs_hba *hba = shost_priv(sdev->host);
> +
> + dev_dbg(hba->dev, "lu %llu scsi device configured", sdev->lun);
> + if (sdev->lun == 2)
> + blk_queue_flag_set(QUEUE_FLAG_SAME_FORCE, sdev->reqeust_queue);
> +}
There are no block drivers in the upstream kernel that set
QUEUE_FLAG_SAME_FORCE. An explanation is missing from the patch
description why this flag is set from the UFS driver instead of by
writing the value "2" into /sys/class/block/$bdev/queue/rq_affinity.
Additionally, an explanation is missing why QUEUE_FLAG_SAME_FORCE is
set but QUEUE_FLAG_SAME_COMP not.
Bart.
Powered by blists - more mailing lists