From: Simon Horman <horms@kernel.org>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, gakula@marvell.com,
hkelam@marvell.com, sgoutham@marvell.com, lcherian@marvell.com,
bbhushan2@marvell.com, jerinj@marvell.com,
netdev@vger.kernel.org
Subject: Re: [net v2] octeontx2-pf: Do not reallocate all ntuple filters
Date: Tue, 13 May 2025 14:25:42 +0100 [thread overview]
Message-ID: <20250513132542.GA3339421@horms.kernel.org> (raw)
In-Reply-To: <1747054357-5850-1-git-send-email-sbhatta@marvell.com>
On Mon, May 12, 2025 at 06:22:37PM +0530, Subbaraya Sundeep wrote:
> If ntuple filters count is modified followed by
> unicast filters count using devlink then the ntuple count
> set by user is ignored and all the ntuple filters are
> being reallocated. Fix this by storing the ntuple count
> set by user. Without this patch, say if user tries
> to modify ntuple count as 8 followed by ucast filter count as 4
> using devlink commands then ntuple count is being reverted to
> default value 16 i.e, not retaining user set value 8.
>
> Fixes: 39c469188b6d ("octeontx2-pf: Add ucast filter count configurability via devlink.")
> Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
I don't think there is any need to repost because of this, but for future
reference it is normal to include the PATCH keyword along with the net
keyword in the Subject.
e.g. Subject: [PATCH net v2] ...
Likewise for net-next.
next prev parent reply other threads:[~2025-05-13 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 12:52 [net v2] octeontx2-pf: Do not reallocate all ntuple filters Subbaraya Sundeep
2025-05-13 13:25 ` Simon Horman [this message]
2025-05-15 10:50 ` patchwork-bot+netdevbpf
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=20250513132542.GA3339421@horms.kernel.org \
--to=horms@kernel.org \
--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=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--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).