public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: sgoutham@marvell.com, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCv4 net-next] octeontx2-pf: Add RSS multi group support
Date: Tue, 12 Jan 2021 15:16:10 -0800	[thread overview]
Message-ID: <5f140376c36bbe47edeb8784ada3b74fafe05afe.camel@kernel.org> (raw)
In-Reply-To: <20210104072039.27297-1-gakula@marvell.com>

On Mon, 2021-01-04 at 12:50 +0530, Geetha sowjanya wrote:
> Hardware supports 8 RSS groups per interface. Currently we are using
> only group '0'. This patch allows user to create new RSS
> groups/contexts
> and use the same as destination for flow steering rules.
> 
> usage:
> To steer the traffic to RQ 2,3
> 
> ethtool -X eth0 weight 0 0 1 1 context new
> (It will print the allocated context id number)
> New RSS context is 1
> 
> ethtool -N eth0 flow-type tcp4 dst-port 80 context 1 loc 1
> 
> To delete the context
> ethtool -X eth0 context 1 delete
> 
> When an RSS context is removed, the active classification
> rules using this context are also removed.
> 
> Change-log:
> 
> v4
> - Fixed compiletime warning.
> - Address Saeed's comments on v3.
> 

This patch is marked as accepted in patchwork
https://patchwork.kernel.org/project/netdevbpf/patch/20210104072039.27297-1-gakula@marvell.com/

but it is not actually applied, maybe resend..


you can add:
Reviewed-by: Saeed Mahameed <saeedm@nvidia.com>



  parent reply	other threads:[~2021-01-12 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04  7:20 [PATCv4 net-next] octeontx2-pf: Add RSS multi group support Geetha sowjanya
2021-01-12  4:17 ` Geethasowjanya Akula
2021-01-12 23:03   ` Jakub Kicinski
2021-01-12 23:16 ` Saeed Mahameed [this message]
2021-01-12 23:18   ` Saeed Mahameed

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=5f140376c36bbe47edeb8784ada3b74fafe05afe.camel@kernel.org \
    --to=saeed@kernel.org \
    --cc=davem@davemloft.net \
    --cc=gakula@marvell.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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