From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next 3/3] ice: Handle LLDP MIB Pending change
Date: Fri, 29 Jul 2022 11:55:17 -0700 [thread overview]
Message-ID: <5847d865-6959-9ff7-a92a-dffdc503b780@intel.com> (raw)
In-Reply-To: <20220728140426.664140-4-anatolii.gerasymenko@intel.com>
On 7/28/2022 7:04 AM, Anatolii Gerasymenko wrote:
> If the number of Traffic Classes (TC) is decreased, the FW will no
> longer remove TC nodes, but will send a pending change notification. This
> will allow RDMA to destroy corresponding Control QP markers. After RDMA
> finishes outstanding operations, the ice driver will send an execute MIB
> Pending change admin queue command to FW to finish DCB configuration
> change.
>
> The FW will buffer all incoming Pending changes, so there can be only
> one active Pending change.
>
> RDMA driver guarantees to remove Control QP markers within 5000 ms.
> Hence, LLDP response timeout txTTL (default 30 sec) will be met.
>
> Signed-off-by: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_dcb_lib.c | 25 ++++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_dcb_lib.c b/drivers/net/ethernet/intel/ice/ice_dcb_lib.c
> index 1c54eb643b6f..f16e4c54409f 100644
> --- a/drivers/net/ethernet/intel/ice/ice_dcb_lib.c
> +++ b/drivers/net/ethernet/intel/ice/ice_dcb_lib.c
> @@ -933,6 +933,16 @@ ice_tx_prepare_vlan_flags_dcb(struct ice_tx_ring *tx_ring,
> }
> }
>
> +/**
> + * ice_dcb_is_mib_change_pending - Check if MIB change is pending
> + * @state: MIB change state
> + */
> +static inline bool ice_dcb_is_mib_change_pending(u8 state)
No 'inline' in .c files
> +{
> + return ICE_AQ_LLDP_MIB_CHANGE_PENDING ==
> + FIELD_GET(ICE_AQ_LLDP_MIB_CHANGE_STATE_M, state);
> +}
> +
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-07-29 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 14:04 [Intel-wired-lan] [PATCH net-next 0/3] ice: Implement LLDP MIB Pending change Anatolii Gerasymenko
2022-07-28 14:04 ` [Intel-wired-lan] [PATCH net-next 1/3] ice: Add 'Execute Pending LLDP MIB' Admin Queue command Anatolii Gerasymenko
2022-07-28 14:04 ` [Intel-wired-lan] [PATCH net-next 2/3] ice: Get DCBX config from LLDP MIB change event Anatolii Gerasymenko
2022-07-28 14:04 ` [Intel-wired-lan] [PATCH net-next 3/3] ice: Handle LLDP MIB Pending change Anatolii Gerasymenko
2022-07-29 18:55 ` Tony Nguyen [this message]
2022-08-01 8:06 ` Anatolii Gerasymenko
2022-08-01 15:52 ` Tony Nguyen
2022-08-02 10:30 ` Anatolii Gerasymenko
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=5847d865-6959-9ff7-a92a-dffdc503b780@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=anatolii.gerasymenko@intel.com \
--cc=intel-wired-lan@lists.osuosl.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