From: Bart Van Assche <bvanassche@acm.org>
To: hyenc.jeong@samsung.com,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Cc: ALIM AKHTAR <alim.akhtar@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jinyoung Choi <j-young.choi@samsung.com>,
Dukhyun Kwon <d_hyun.kwon@samsung.com>,
Jeuk Kim <jeuk20.kim@samsung.com>,
Keoseong Park <keosung.park@samsung.com>,
Jaemyung Lee <jaemyung.lee@samsung.com>,
Jieon Seol <jieon.seol@samsung.com>,
Gyusun Lee <gyusun.lee@samsung.com>,
Yunjae Jo <yunjae00.jo@samsung.com>
Subject: Re: [PATCH] scsi: ufs: Add support for the aggregated read query opcode
Date: Fri, 10 Jul 2026 07:46:55 -0700 [thread overview]
Message-ID: <6d087f28-5795-4929-b5d3-3f78d9b9bc60@acm.org> (raw)
In-Reply-To: <20260710054556epcms2p68986e2af26f42e63c87ab8fde034e450@epcms2p6>
On 7/9/26 10:45 PM, Hyeoncheol Jeong wrote:
> struct utp_transfer_cmd_desc {
> u8 command_upiu[ALIGNED_UPIU_SIZE];
> - u8 response_upiu[ALIGNED_UPIU_SIZE];
> + u8 response_upiu[ALIGNED_RSP_UPIU_SIZE];
> u8 prd_table[];
> };
This change increases the size of every CQ entry and also of every LRB
entry by about 4 KiB. This is not acceptable.
Bart.
next prev parent reply other threads:[~2026-07-10 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260710053524epcms2p82121eba4240c37112fc5669430035442@epcms2p6>
2026-07-10 5:45 ` Hyeoncheol Jeong
2026-07-10 14:46 ` Bart Van Assche [this message]
[not found] ` <CGME20260710053524epcms2p82121eba4240c37112fc5669430035442@epcms2p4>
2026-07-13 2:52 ` Hyeoncheol Jeong
2026-07-13 12:55 ` Bart Van Assche
2026-07-16 2:51 ` Hyeoncheol Jeong
2026-07-22 8:48 ` [PATCH v2] " Hyeoncheol Jeong
2026-07-22 17:08 ` Bart Van Assche
[not found] ` <CGME20260710053524epcms2p82121eba4240c37112fc5669430035442@epcms2p1>
2026-07-23 7:47 ` Hyeoncheol Jeong
2026-07-23 19:27 ` Bart Van Assche
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=6d087f28-5795-4929-b5d3-3f78d9b9bc60@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=d_hyun.kwon@samsung.com \
--cc=gyusun.lee@samsung.com \
--cc=hyenc.jeong@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jaemyung.lee@samsung.com \
--cc=jeuk20.kim@samsung.com \
--cc=jieon.seol@samsung.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=yunjae00.jo@samsung.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
all inboxes | Powered by JetHome®