From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <gakula@marvell.com>, <hkelam@marvell.com>,
<sgoutham@marvell.com>, <lcherian@marvell.com>,
<bbhushan2@marvell.com>, <jerinj@marvell.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net v2] octeontx2-af: Send Link events one by one
Date: Thu, 15 May 2025 16:35:14 +0000 [thread overview]
Message-ID: <aCYXwo-0CfHYGhh9@3958e7e617f8> (raw)
In-Reply-To: <aCRQNJbYL2ORGmMh@mev-dev.igk.intel.com>
Hi Michal,
On 2025-05-14 at 08:11:32, Michal Swiatkowski (michal.swiatkowski@linux.intel.com) wrote:
> On Wed, May 14, 2025 at 11:58:28AM +0530, Subbaraya Sundeep wrote:
> > Send link events one after another otherwise new message
> > is overwriting the message which is being processed by PF.
> >
> > Fixes: a88e0f936ba9 ("octeontx2: Detect the mbox up or down message via register")
> > Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
> > ---
> > v2:
> > No changes. Added subject prefix net.
> >
> > drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c b/drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c
> > index 992fa0b..ebb56eb 100644
> > --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c
> > +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_cgx.c
> > @@ -272,6 +272,8 @@ static void cgx_notify_pfs(struct cgx_link_event *event, struct rvu *rvu)
> >
> > otx2_mbox_msg_send_up(&rvu->afpf_wq_info.mbox_up, pfid);
> >
> > + otx2_mbox_wait_for_rsp(&rvu->afpf_wq_info.mbox_up, pfid);
> > +
> > mutex_unlock(&rvu->mbox_lock);
>
> Fix looks fine.
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>
> In rvu_rep_up_notify() the same send function is called (and
> rvu_rep_up_notify() is called in do, while loop in
> rvu_rep_wq_handler()). Doesn't it also need waiting for response?
> Are there a message that don't need waiting? Maybe it will be best to
> always wait for response if another call can overwrite.
>
> Thanks
>
Okay I will modify rvu_rep_up_notify, test and send next version along
with this.
Thanks,
Sundeep
> > } while (pfmap);
> > }
> > --
> > 2.7.4
next prev parent reply other threads:[~2025-05-15 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 6:28 [PATCH net v2] octeontx2-af: Send Link events one by one Subbaraya Sundeep
2025-05-14 8:11 ` Michal Swiatkowski
2025-05-15 16:35 ` Subbaraya Sundeep [this message]
2025-05-15 14:12 ` Jakub Kicinski
2025-05-15 16:41 ` Subbaraya Sundeep
2025-05-15 17:19 ` Jakub Kicinski
2025-05-15 17:34 ` Subbaraya Sundeep
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=aCYXwo-0CfHYGhh9@3958e7e617f8 \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.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;
as well as URLs for NNTP newsgroup(s).