From: Stephen Hemminger <stephen@networkplumber.org>
To: madhuker.mythri@oracle.com
Cc: chas3@att.com, dev@dpdk.org, tomaszx.kulasek@intel.com
Subject: Re: [PATCH] net/bonding: avoid RSS reta update in flow-isolation mode
Date: Mon, 7 Jul 2025 09:41:47 -0700 [thread overview]
Message-ID: <20250707094147.6b33b994@hermes.local> (raw)
In-Reply-To: <20250704135031.5306-1-madhuker.mythri@oracle.com>
On Fri, 4 Jul 2025 19:20:31 +0530
madhuker.mythri@oracle.com wrote:
> From: Madhuker Mythri <madhuker.mythri@oracle.com>
>
> In bonding PMD, member_start() function checks whether RSS(mq_mode) is
> enabled and then calling the RSS rte_eth_dev_rss_reta_update() API, which
> is returning error in-case of device configured in flow isolation-mode.
> When the device configured with flow isolation mode RSS reta update is not
> required and the API was not supported. For example in-case of mlx5 PMD,
> RSS reta update API was not supported, when the device is configured in
> flow isolation-mode.
>
> So, added check to verify if the device is configured in flow-isolation
> mode, then do not call the rte_eth_dev_rss_reta_update() API.
>
> Fixes: 734ce47f71e0 ("bonding: support RSS dynamic configuration")
> Cc: tomaszx.kulasek@intel.com
>
> Signed-off-by: Madhuker Mythri <madhuker.mythri@oracle.com>
Applied to next-net.
Next time please use patch versions (ie [PATCH v2] etc) and thread
the followups to the original patch.
This is described in https://doc.dpdk.org/guides/contributing/patches.html#creating-patches
It helps tools like patchwork and with reviewers so that we know which
version supersedes.
next prev parent reply other threads:[~2025-07-07 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 13:50 madhuker.mythri
2025-07-07 16:41 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-04 13:22 madhuker.mythri
2025-07-03 11:59 madhuker.mythri
2025-07-03 16:23 ` Stephen Hemminger
2025-07-03 11:37 madhuker.mythri
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=20250707094147.6b33b994@hermes.local \
--to=stephen@networkplumber.org \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=madhuker.mythri@oracle.com \
--cc=tomaszx.kulasek@intel.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).