From: Jens Axboe <axboe@kernel.dk>
To: Bin Liu <b-liu@ti.com>,
linux-block@vger.kernel.org, linux-mmc@vger.kernel.org
Cc: ulf.hansson@linaro.org, shawn.lin@linux.dev
Subject: Re: [PATCH v3] mmc: block: use single block write in retry
Date: Wed, 25 Mar 2026 08:12:36 -0600 [thread overview]
Message-ID: <b4c84630-ff69-4d1c-8b82-815679d3fa72@kernel.dk> (raw)
In-Reply-To: <20260325134947.2799552-1-b-liu@ti.com>
On 3/25/26 7:49 AM, Bin Liu wrote:
> diff --git a/drivers/mmc/core/queue.h b/drivers/mmc/core/queue.h
> index 1498840a4ea0..c254e6580afd 100644
> --- a/drivers/mmc/core/queue.h
> +++ b/drivers/mmc/core/queue.h
> @@ -61,6 +61,8 @@ enum mmc_drv_op {
> MMC_DRV_OP_GET_EXT_CSD,
> };
>
> +#define MQRQ_XFER_SINGLE_BLOCK BIT(0)
> +
> struct mmc_queue_req {
> struct mmc_blk_request brq;
> struct scatterlist *sg;
> @@ -69,6 +71,7 @@ struct mmc_queue_req {
> void *drv_op_data;
> unsigned int ioc_count;
> int retries;
> + u32 flags;
> };
>
> struct mmc_queue {
I'm assuming retries is a pretty small number (didn't check), so if you
care about layout/space in mmc_queue_req, you could make this:
u16 retries;
u16 flags;
and not grow the size of it by 8 bytes with that addition.
Not a huge deal, obviously, but always good to consider things like that
to avoid wasting memory for nothing.
--
Jens Axboe
next prev parent reply other threads:[~2026-03-25 14:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 16:04 [PATCH] mmc: block: use single block write in retry Bin Liu
2026-03-16 15:01 ` Ulf Hansson
2026-03-16 16:22 ` Bin Liu
2026-03-24 12:44 ` Ulf Hansson
2026-03-17 12:46 ` Shawn Lin
2026-03-17 13:24 ` Bin Liu
2026-03-18 1:43 ` Shawn Lin
2026-03-18 14:55 ` Bin Liu
2026-03-18 15:10 ` Bin Liu
2026-03-18 15:17 ` Bin Liu
2026-03-23 13:05 ` Bin Liu
2026-03-24 7:34 ` Shawn Lin
2026-03-24 14:34 ` [PATCH v2 0/2] " Bin Liu
2026-03-24 14:34 ` [PATCH v2 1/2] block: define new rqf_flags RQF_XFER_SINGLE_BLK Bin Liu
2026-03-24 18:48 ` Jens Axboe
2026-03-24 19:11 ` Bin Liu
2026-03-24 19:16 ` Jens Axboe
2026-03-24 20:41 ` Bin Liu
2026-03-24 14:34 ` [PATCH v2 2/2] mmc: block: use single block write in retry Bin Liu
2026-03-24 14:57 ` [PATCH v2 0/2] " Ulf Hansson
2026-03-24 19:17 ` Jens Axboe
2026-03-25 13:49 ` [PATCH v3] " Bin Liu
2026-03-25 14:12 ` Jens Axboe [this message]
2026-03-25 14:21 ` Bin Liu
2026-03-25 14:23 ` Jens Axboe
2026-03-25 14:27 ` Bin Liu
2026-03-25 15:22 ` Ulf Hansson
2026-03-25 15:29 ` Bin Liu
2026-03-26 12:33 ` Ulf Hansson
2026-03-26 13:41 ` Bin Liu
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=b4c84630-ff69-4d1c-8b82-815679d3fa72@kernel.dk \
--to=axboe@kernel.dk \
--cc=b-liu@ti.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.lin@linux.dev \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox