From: Jiri Pirko <jiri@resnulli.us>
To: Geetha sowjanya <gakula@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, sgoutham@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com
Subject: Re: [net-next PATCH v2 7/9] octeontx2-pf: Add support to sync link state between representor and VFs
Date: Tue, 23 Apr 2024 15:06:32 +0200 [thread overview]
Message-ID: <ZieyWKC7ReztKRWF@nanopsycho> (raw)
In-Reply-To: <20240422095401.14245-8-gakula@marvell.com>
Mon, Apr 22, 2024 at 11:53:59AM CEST, gakula@marvell.com wrote:
>Implements mbox function to sync the link state between VFs and
>its representors. Same mbox is use to notify other updates like mtu etc.
>
>This patch enables
>- Reflecting the link state of representor based on the VF state and
> link state of VF based on representor.
Could you please elaborate a bit more how exactly this behaves? Examples
would help.
>- On VF interface up/down a notification is sent via mbox to representor
> to update the link state.
>- On representor interafce up/down will cause the link state update of VF.
>
next prev parent reply other threads:[~2024-04-23 13:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 9:53 [net-next PATCH v2 0/9] Introduce RVU representors Geetha sowjanya
2024-04-22 9:53 ` [net-next PATCH v2 1/9] octeontx2-pf: Refactoring RVU driver Geetha sowjanya
2024-04-22 9:53 ` [net-next PATCH v2 2/9] octeontx2-pf: RVU representor driver Geetha sowjanya
2024-04-22 16:58 ` Jiri Pirko
2024-04-23 15:23 ` [EXTERNAL] " Geethasowjanya Akula
2024-04-22 9:53 ` [net-next PATCH v2 3/9] octeontx2-pf: Create representor netdev Geetha sowjanya
2024-04-22 17:03 ` Jiri Pirko
2024-04-23 15:26 ` [EXTERNAL] " Geethasowjanya Akula
2024-04-22 9:53 ` [net-next PATCH v2 4/9] octeontx2-pf: Add basic net_device_ops Geetha sowjanya
2024-04-22 9:53 ` [net-next PATCH v2 5/9] octeontx2-af: Add packet path between representor and VF Geetha sowjanya
2024-04-23 13:09 ` Jiri Pirko
2024-04-25 6:01 ` Sunil Kovvuri Goutham
2024-04-25 6:59 ` Jiri Pirko
2024-04-23 16:13 ` kernel test robot
2024-04-22 9:53 ` [net-next PATCH v2 6/9] octeontx2-pf: Get VF stats via representor Geetha sowjanya
2024-04-22 9:53 ` [net-next PATCH v2 7/9] octeontx2-pf: Add support to sync link state between representor and VFs Geetha sowjanya
2024-04-23 13:06 ` Jiri Pirko [this message]
2024-04-23 16:09 ` [EXTERNAL] " Geethasowjanya Akula
2024-04-24 14:41 ` Jiri Pirko
2024-04-25 5:11 ` Geethasowjanya Akula
2024-04-22 9:54 ` [net-next PATCH v2 8/9] octeontx2-pf: Configure VF mtu via representor Geetha sowjanya
2024-04-22 9:54 ` [net-next PATCH v2 9/9] octeontx2-pf: Add representors for sdp MAC Geetha sowjanya
2024-04-23 13:04 ` Jiri Pirko
2024-04-25 6:09 ` Sunil Kovvuri Goutham
2024-04-25 7:01 ` Jiri Pirko
2024-04-23 13:03 ` [net-next PATCH v2 0/9] Introduce RVU representors Jiri Pirko
2024-04-23 15:39 ` [EXTERNAL] " Geethasowjanya Akula
2024-04-24 14:42 ` Jiri Pirko
2024-04-25 5:09 ` Geethasowjanya Akula
2024-04-25 7:00 ` Jiri Pirko
2024-04-28 10:49 ` Geethasowjanya Akula
2024-04-23 13:10 ` Jiri Pirko
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=ZieyWKC7ReztKRWF@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.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).