From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: John Garry <john.garry@huawei.com>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Xiang Chen <chenxiang66@hisilicon.com>,
Jason Yan <yanaijie@huawei.com>,
Luo Jiaxing <luojiaxing@huawei.com>
Subject: Re: [PATCH v3 28/31] scsi: pm8001: Introduce ccb alloc/free helpers
Date: Wed, 16 Feb 2022 20:43:39 +0900 [thread overview]
Message-ID: <4a1cdee3-76fc-0135-16d8-e28d90967dfe@opensource.wdc.com> (raw)
In-Reply-To: <0a0006af-2878-3e6f-dc27-be04d2866fc3@huawei.com>
On 2/15/22 20:07, John Garry wrote:
> On 14/02/2022 02:17, Damien Le Moal wrote:
>> Introduce the pm8001_ccb_alloc() and pm8001_ccb_free() helpers to
>> replace the typical code patterns:
>>
>> res = pm8001_tag_alloc(pm8001_ha, &ccb_tag);
>> if (res)
>> ...
>> ccb = &pm8001_ha->ccb_info[ccb_tag];
>> ccb->device = pm8001_ha_dev;
>> ccb->ccb_tag = ccb_tag;
>> ccb->task = task;
>> ccb->n_elem = 0;A
>
> nit: stray 'A' character
>
>>
>> and
>>
>> ccb->task = NULL;
>> ccb->ccb_tag = PM8001_INVALID_TAG;
>> pm8001_tag_free(pm8001_ha, tag);
>
> Isn't it possible to do a "memset struct members", such that we order
> the members specifically that we can memset(0) a known region? The
> advantage is that adding/removing a member does not require much code to
> be touched and possibly missed.
>
>>
>> With the simpler function calls:
>>
>> ccb = pm8001_ccb_alloc(pm8001_ha, pm8001_ha_dev, task);
>> if (!ccb)
>> ...
>>
>> and
>>
>> pm8001_ccb_free(pm8001_ha, ccb);
>>
>> The pm8001_ccb_alloc() helper ensures that all fields of the ccb info
>> structure for the newly allocated tag are all initialized, except the
>> buf_prd field. The pm8001_ccb_free() helper clears the initialized
>> fields and the ccb tag to ensure that iteration over the adapter
>> ccb_info array detects ccbs that are in use.
>
>
>>
>> All call site of the pm8001_tag_alloc() function that use a ccb info
>> associated with an allocated tag are converted to use the new helpers.
>>
>> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>> ---
>
> The comments are not a show stopper, so:
> Reviewed-by: John Garry <john.garry@huawei.com>
Thanks. I left the patch as-is and did not try the memset() thing. Let's
do that later.
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-02-16 11:43 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 2:17 [PATCH v3 00/31] libsas and pm8001 fixes Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 01/31] scsi: libsas: Fix sas_ata_qc_issue() handling of NCQ NON DATA commands Damien Le Moal
2022-02-14 17:56 ` John Garry
2022-02-14 22:23 ` Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 02/31] scsi: pm8001: Fix __iomem pointer use in pm8001_phy_control() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 03/31] scsi: pm8001: Fix pm8001_update_flash() local variable type Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 04/31] scsi: pm8001: Fix command initialization in pm80XX_send_read_log() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 05/31] scsi: pm8001: Fix pm80xx_pci_mem_copy() interface Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 06/31] scsi: pm8001: Fix command initialization in pm8001_chip_ssp_tm_req() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 07/31] scsi: pm8001: Fix payload initialization in pm80xx_set_thermal_config() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 08/31] scsi: pm8001: Fix le32 values handling in pm80xx_set_sas_protocol_timer_config() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 09/31] scsi: pm8001: Fix payload initialization in pm80xx_encrypt_update() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 10/31] scsi: pm8001: Fix le32 values handling in pm80xx_chip_ssp_io_req() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 11/31] scsi: pm8001: Fix le32 values handling in pm80xx_chip_sata_req() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 12/31] scsi: pm8001: Fix use of struct set_phy_profile_req fields Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 13/31] scsi: pm8001: Remove local variable in pm8001_pci_resume() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 14/31] scsi: pm8001: Fix NCQ NON DATA command task initialization Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 15/31] scsi: pm8001: Fix NCQ NON DATA command completion handling Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 16/31] scsi: pm8001: Fix abort all task initialization Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 17/31] scsi: pm8001: Fix pm8001_tag_alloc() failures handling Damien Le Moal
2022-02-14 18:02 ` John Garry
2022-02-14 2:17 ` [PATCH v3 18/31] scsi: pm8001: Fix pm80xx_chip_phy_ctl_req() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 19/31] scsi: pm8001: Fix pm8001_mpi_task_abort_resp() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 20/31] scsi: pm8001: Fix tag values handling Damien Le Moal
2022-02-15 11:09 ` John Garry
2022-02-15 23:44 ` Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 21/31] scsi: pm8001: Fix task leak in pm8001_send_abort_all() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 22/31] scsi: pm8001: Fix tag leaks on error Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 23/31] scsi: pm8001: fix memory leak in pm8001_chip_fw_flash_update_req() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 24/31] scsi: pm8001: Fix process_one_iomb() kdoc comment Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 25/31] scsi: libsas: Simplify sas_ata_qc_issue() detection of NCQ commands Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 26/31] scsi: pm8001: Simplify pm8001_get_ncq_tag() Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 27/31] scsi: pm8001: Cleanup pm8001_queue_command() Damien Le Moal
2022-02-15 10:55 ` John Garry
2022-02-16 11:36 ` Damien Le Moal
2022-02-16 11:38 ` John Garry
2022-02-16 11:42 ` Damien Le Moal
2022-02-16 11:50 ` John Garry
2022-02-16 12:05 ` Damien Le Moal
2022-02-16 12:21 ` John Garry
2022-02-17 0:12 ` Damien Le Moal
2022-02-17 9:23 ` John Garry
2022-02-17 10:47 ` Damien Le Moal
2022-02-17 12:49 ` John Garry
2022-02-18 3:12 ` Damien Le Moal
2022-02-18 11:21 ` John Garry
2022-02-17 11:47 ` Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 28/31] scsi: pm8001: Introduce ccb alloc/free helpers Damien Le Moal
2022-02-15 11:07 ` John Garry
2022-02-15 23:41 ` Damien Le Moal
2022-02-16 11:43 ` Damien Le Moal [this message]
2022-02-14 2:17 ` [PATCH v3 29/31] scsi: pm8001: Simplify pm8001_mpi_build_cmd() interface Damien Le Moal
2022-02-14 2:17 ` [PATCH v3 30/31] scsi: pm8001: Simplify pm8001_task_exec() Damien Le Moal
2022-02-15 8:57 ` John Garry
2022-02-14 2:17 ` [PATCH v3 31/31] scsi: pm8001: Simplify pm8001_ccb_task_free() Damien Le Moal
2022-02-14 2:23 ` [PATCH v3 00/31] libsas and pm8001 fixes Damien Le Moal
2022-02-15 3:18 ` Martin K. Petersen
2022-02-15 7:38 ` Damien Le Moal
2022-02-14 18:06 ` John Garry
2022-02-14 22:29 ` Damien Le Moal
2022-02-15 8:16 ` John Garry
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=4a1cdee3-76fc-0135-16d8-e28d90967dfe@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=chenxiang66@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luojiaxing@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@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