From: Paolo Abeni <pabeni@redhat.com>
To: Leo Yang <leo.yang.sy0@gmail.com>,
jk@codeconstruct.com.au, matt@codeconstruct.com.au,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Leo Yang <Leo-Yang@quantatw.com>
Subject: Re: [PATCH net v2] mctp i3c: fix MCTP I3C driver multi-thread issue
Date: Thu, 9 Jan 2025 11:59:25 +0100 [thread overview]
Message-ID: <4abb5ce6-394e-47dd-ad02-ed75a8aa42e1@redhat.com> (raw)
In-Reply-To: <20250107031529.3296094-1-Leo-Yang@quantatw.com>
On 1/7/25 4:15 AM, Leo Yang wrote:
> We found a timeout problem with the pldm command on our system. The
> reason is that the MCTP-I3C driver has a race condition when receiving
> multiple-packet messages in multi-thread, resulting in a wrong packet
> order problem.
>
> We identified this problem by adding a debug message to the
> mctp_i3c_read function.
>
> According to the MCTP spec, a multiple-packet message must be composed
> in sequence, and if there is a wrong sequence, the whole message will be
> discarded and wait for the next SOM.
> For example, SOM → Pkt Seq #2 → Pkt Seq #1 → Pkt Seq #3 → EOM.
>
> Therefore, we try to solve this problem by adding a mutex to the
> mctp_i3c_read function. Before the modification, when a command
> requesting a multiple-packet message response is sent consecutively, an
> error usually occurs within 100 loops. After the mutex, it can go
> through 40000 loops without any error, and it seems to run well.
>
> But I'm a little worried about the performance of mutex in high load
> situation (as spec seems to allow different endpoints to respond at the
> same time), do you think this is a feasible solution?
For the record, I'm taking the liberty of dropping the above paragraph
from the changelog, as the question IMHO should have been placed after
the --- separator, has been already replied and repost just for this
change would consume more time from everyone.
Cheers,
Paolo
next prev parent reply other threads:[~2025-01-09 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 3:15 [PATCH net v2] mctp i3c: fix MCTP I3C driver multi-thread issue Leo Yang
2025-01-09 10:59 ` Paolo Abeni [this message]
2025-01-09 11:10 ` patchwork-bot+netdevbpf
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=4abb5ce6-394e-47dd-ad02-ed75a8aa42e1@redhat.com \
--to=pabeni@redhat.com \
--cc=Leo-Yang@quantatw.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=leo.yang.sy0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@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