From: Frank Li <Frank.li@oss.nxp.com>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i3c: dw: make struct dw_i3c_cmd smaller
Date: Fri, 14 Aug 2026 12:59:59 -0400 [thread overview]
Message-ID: <an9JjwCdeLxcIVmd@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <an6SJAnIl_wdTPNA@xhacker>
On Fri, Aug 14, 2026 at 11:57:24AM +0800, Jisheng Zhang wrote:
> On Thu, Aug 13, 2026 at 04:38:32PM -0400, Frank Li wrote:
> > On Thu, Aug 13, 2026 at 12:46:03PM +0800, Jisheng Zhang wrote:
> > > The dw_i3c_cmd is dynamically allocated, make it smaller. For example
> > > on 64bit platforms, we reduce the size from 48 bytes to 32 bytes.
> > >
> > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> > > ---
> > > drivers/i3c/master/dw-i3c-master.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/i3c/master/dw-i3c-master.c b/drivers/i3c/master/dw-i3c-master.c
> > > index 6ba84a97765f..d6f84f0f4c2d 100644
> > > --- a/drivers/i3c/master/dw-i3c-master.c
> > > +++ b/drivers/i3c/master/dw-i3c-master.c
> > > @@ -247,10 +247,10 @@ struct dw_i3c_cmd {
> > > u32 cmd_lo;
> > > u32 cmd_hi;
> > > u16 tx_len;
> > > - const void *tx_buf;
> > > u16 rx_len;
> >
> > only switch rx_len and tx_buf should be enough. otherwise there are data
> > pad after u8 error.
>
> If we keep the error at the end of the struct, there's still padding
> after the u8 error.
> There's no big difference between current sol and only switch rx_len and
> tx_buf on 32bit platforms. But on 64bit platforms, the current version
> makes use of the pad to store the error, thus saves 8 byte more.
Yes, I missed caculate.
Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> Thanks
> >
> > Frank
> >
> > > - void *rx_buf;
> > > u8 error;
> > > + const void *tx_buf;
> > > + void *rx_buf;
> > > };
> > >
> > > struct dw_i3c_xfer {
> > > --
> > > 2.51.0
> > >
next prev parent reply other threads:[~2026-08-14 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 4:46 Jisheng Zhang
2026-08-13 20:38 ` Frank Li
2026-08-14 3:57 ` Jisheng Zhang
2026-08-14 16:59 ` Frank Li [this message]
2026-08-18 21:09 ` Alexandre Belloni
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=an9JjwCdeLxcIVmd@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jszhang@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®