<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> Thank you for your reply. Personally, I think that when disabling promiscuous/all-multicast mode, the corresponding flag should be set based on the return value. This is because, at the driver implementation level, the driver may check the flag to determine whether the corresponding disable operation needs to be executed. If the flag is set before the operation is completed, the driver will not execute the operation when it checks the flag, as it will find that the flag has already been set.<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> 发件人: Stephen Hemminger <stephen@networkplumber.org> 发送时间: 2025年5月8日 13:35 收件人: Sunyang Wu <sunyang.wu@jaguarmicro.com> 抄送: dev <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>; Ferruh Yigit <ferruh.yigit@amd.com>; Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> 主题: Re: [PATCH] ethdev: optimize how the values of the flag variables are assigned<o:p></o:p> </div> </div> <o:p> </o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%"> <tbody> <tr> <td style="background:red;padding:5.0pt 2.0pt 5.0pt 2.0pt"></td> <td width="100%" style="width:100.0%;background:#FFD4D4;padding:5.0pt 4.0pt 5.0pt 12.0pt;wrap:break-word"> <div> External Mail: This email originated from OUTSIDE of the organization! Do not click links, open attachments or provide ANY information unless you recognize the sender and know the content is safe. <o:p></o:p> </div> </td> </tr> </tbody> </table> <o:p> </o:p> <div> Why bother? This is not critical path. <o:p></o:p> <div> Original code looked fine <o:p></o:p> </div> </div> <o:p> </o:p> <div> On Thu, May 8, 2025, 11:34 Sunyang Wu <<a href="mailto:sunyang.wu@jaguarmicro.com">sunyang.wu@jaguarmicro.com</a>> wrote:<o:p></o:p> </div> Set the values of the promiscuous and all_multicast variables according to the return value. Signed-off-by: Sunyang Wu <<a href="mailto:sunyang.wu@jaguarmicro.com" target="_blank">sunyang.wu@jaguarmicro.com</a>> --- lib/ethdev/rte_ethdev.c | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/lib/ethdev/rte_ethdev.c b/lib/ethdev/rte_ethdev.c index d4197322a0..b1f593edc4 100644 --- a/lib/ethdev/rte_ethdev.c +++ b/lib/ethdev/rte_ethdev.c @@ -3044,10 +3044,8 @@ rte_eth_promiscuous_disable(uint16_t port_id) if (dev->dev_ops->promiscuous_disable == NULL) return -ENOTSUP; - dev->data->promiscuous = 0; diag = dev->dev_ops->promiscuous_disable(dev); - if (diag != 0) - dev->data->promiscuous = 1; + dev->data->promiscuous = (diag == 0) ? 0 : 1; diag = eth_err(port_id, diag); @@ -3112,10 +3110,9 @@ rte_eth_allmulticast_disable(uint16_t port_id) if (dev->dev_ops->allmulticast_disable == NULL) return -ENOTSUP; - dev->data->all_multicast = 0; + diag = dev->dev_ops->allmulticast_disable(dev); - if (diag != 0) - dev->data->all_multicast = 1; + dev->data->all_multicast = (diag == 0) ? 0 : 1; diag = eth_err(port_id, diag); -- 2.19.0.rc0.windows.1<o:p></o:p> </div> </body> </html>