All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@mellanox.com,
	mlxsw@mellanox.com, Ido Schimmel <idosch@mellanox.com>
Subject: [PATCH net-next 0/9] mlxsw: spectrum: Enforce some HW limitations for matchall TC offload
Date: Sat,  9 May 2020 23:06:01 +0300	[thread overview]
Message-ID: <20200509200610.375719-1-idosch@idosch.org> (raw)

From: Ido Schimmel <idosch@mellanox.com>

Jiri says:

There are some limitations for TC matchall classifier offload that are
given by the mlxsw HW dataplane. It is not possible to do sampling on
egress and also the mirror/sample vs. ACL (flower) ordering is fixed. So
check this and forbid to offload incorrect setup.

Jiri Pirko (9):
  mlxsw: spectrum_matchall: Restrict sample action to be allowed only on
    ingress
  mlxsw: spectrum_flower: Expose a function to get min and max rule
    priority
  mlxsw: spectrum_matchall: Put matchall list into substruct of flow
    struct
  mlxsw: spectrum_matchall: Expose a function to get min and max rule
    priority
  mlxsw: spectrum_matchall: Forbid to insert matchall rules in collision
    with flower rules
  mlxsw: spectrum_flower: Forbid to insert flower rules in collision
    with matchall rules
  selftests: mlxsw: rename tc_flower_restrictions.sh to
    tc_restrictions.sh
  selftests: mlxsw: tc_restrictions: add test to check sample action
    restrictions
  selftests: mlxsw: tc_restrictions: add couple of test for the correct
    matchall-flower ordering

 .../net/ethernet/mellanox/mlxsw/spectrum.h    |  18 ++-
 .../ethernet/mellanox/mlxsw/spectrum_acl.c    |  13 +-
 .../mellanox/mlxsw/spectrum_acl_tcam.c        |  39 +++++-
 .../mellanox/mlxsw/spectrum_acl_tcam.h        |   3 +-
 .../ethernet/mellanox/mlxsw/spectrum_flow.c   |   6 +-
 .../ethernet/mellanox/mlxsw/spectrum_flower.c |  52 +++++++
 .../mellanox/mlxsw/spectrum_matchall.c        |  86 +++++++++++-
 ...wer_restrictions.sh => tc_restrictions.sh} | 132 ++++++++++++++++++
 8 files changed, 332 insertions(+), 17 deletions(-)
 rename tools/testing/selftests/drivers/net/mlxsw/{tc_flower_restrictions.sh => tc_restrictions.sh} (53%)

-- 
2.26.2


             reply	other threads:[~2020-05-09 20:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 20:06 Ido Schimmel [this message]
2020-05-09 20:06 ` [PATCH net-next 1/9] mlxsw: spectrum_matchall: Restrict sample action to be allowed only on ingress Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 2/9] mlxsw: spectrum_flower: Expose a function to get min and max rule priority Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 3/9] mlxsw: spectrum_matchall: Put matchall list into substruct of flow struct Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 4/9] mlxsw: spectrum_matchall: Expose a function to get min and max rule priority Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 5/9] mlxsw: spectrum_matchall: Forbid to insert matchall rules in collision with flower rules Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 6/9] mlxsw: spectrum_flower: Forbid to insert flower rules in collision with matchall rules Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 7/9] selftests: mlxsw: rename tc_flower_restrictions.sh to tc_restrictions.sh Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 8/9] selftests: mlxsw: tc_restrictions: add test to check sample action restrictions Ido Schimmel
2020-05-09 20:06 ` [PATCH net-next 9/9] selftests: mlxsw: tc_restrictions: add couple of test for the correct matchall-flower ordering Ido Schimmel
2020-05-09 23:05 ` [PATCH net-next 0/9] mlxsw: spectrum: Enforce some HW limitations for matchall TC offload Jakub Kicinski

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=20200509200610.375719-1-idosch@idosch.org \
    --to=idosch@idosch.org \
    --cc=davem@davemloft.net \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.