All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, oss-drivers@corigine.com,
	Hui Zhou <hui.zhou@corigine.com>,
	Ziyang Chen <ziyang.chen@corigine.com>
Subject: [PATCH net-next 0/3] nfp: flower: police validation and ct enhancements
Date: Wed, 14 Sep 2022 17:06:01 +0100	[thread overview]
Message-ID: <20220914160604.1740282-1-simon.horman@corigine.com> (raw)

Hi,

this series enhances the flower hardware offload
facility provided by the nfp driver.

1. Add validation of police actions created independently of flows

2. Add support offload of ct NAT action

3. Support offload of rule which has both vlan push/pop/mangle
   and ct action

Hui Zhou (2):
  nfp: flower: support hw offload for ct nat action
  nfp: flower: support vlan action in pre_ct

Ziyang Chen (1):
  nfp: flower: add validation of for police actions which are
    independent of flows

 .../ethernet/netronome/nfp/flower/conntrack.c | 242 +++++++++++++++++-
 .../ethernet/netronome/nfp/flower/conntrack.h |   6 +
 .../ethernet/netronome/nfp/flower/qos_conf.c  |  31 ++-
 3 files changed, 263 insertions(+), 16 deletions(-)

-- 
2.30.2


             reply	other threads:[~2022-09-14 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 16:06 Simon Horman [this message]
2022-09-14 16:06 ` [PATCH net-next 1/3] nfp: flower: add validation of for police actions which are independent of flows Simon Horman
2022-09-14 16:06 ` [PATCH net-next 2/3] nfp: flower: support hw offload for ct nat action Simon Horman
2022-09-14 16:06 ` [PATCH net-next 3/3] nfp: flower: support vlan action in pre_ct Simon Horman
2022-09-20 20:40 ` [PATCH net-next 0/3] nfp: flower: police validation and ct enhancements 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=20220914160604.1740282-1-simon.horman@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=davem@davemloft.net \
    --cc=hui.zhou@corigine.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=ziyang.chen@corigine.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 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.