All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org,
	alexandre.belloni@bootlin.com, andrew@lunn.ch,
	claudiu.manoil@nxp.com, xiyou.wangcong@gmail.com,
	f.fainelli@gmail.com, idosch@nvidia.com, jhs@mojatatu.com,
	jiri@resnulli.us, leon@kernel.org, michael.chan@broadcom.com,
	ozsh@nvidia.com, petrm@nvidia.com, roid@nvidia.com,
	saeedm@nvidia.com, vivien.didelot@gmail.com, vladbu@nvidia.com,
	vladimir.oltean@nxp.com, baowen.zheng@corigine.com,
	louis.peens@corigine.com, UNGLinuxDriver@microchip.com,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH v8 net-next 00/13] allow user to offload tc action to net device
Date: Sun, 19 Dec 2021 14:30:12 +0000	[thread overview]
Message-ID: <163992421261.25478.13959206033604654129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211217181629.28081-1-simon.horman@corigine.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 17 Dec 2021 19:16:16 +0100 you wrote:
> Baowen Zheng says:
> 
> Allow use of flow_indr_dev_register/flow_indr_dev_setup_offload to offload
> tc actions independent of flows.
> 
> The motivation for this work is to prepare for using TC police action
> instances to provide hardware offload of OVS metering feature - which calls
> for policers that may be used by multiple flows and whose lifecycle is
> independent of any flows that use them.
> 
> [...]

Here is the summary with links:
  - [v8,net-next,01/13] flow_offload: fill flags to action structure
    https://git.kernel.org/netdev/net-next/c/40bd094d65fc
  - [v8,net-next,02/13] flow_offload: reject to offload tc actions in offload drivers
    https://git.kernel.org/netdev/net-next/c/144d4c9e800d
  - [v8,net-next,03/13] flow_offload: add index to flow_action_entry structure
    https://git.kernel.org/netdev/net-next/c/5a9959008fb6
  - [v8,net-next,04/13] flow_offload: rename offload functions with offload instead of flow
    https://git.kernel.org/netdev/net-next/c/9c1c0e124ca2
  - [v8,net-next,05/13] flow_offload: add ops to tc_action_ops for flow action setup
    https://git.kernel.org/netdev/net-next/c/c54e1d920f04
  - [v8,net-next,06/13] flow_offload: allow user to offload tc action to net device
    https://git.kernel.org/netdev/net-next/c/8cbfe939abe9
  - [v8,net-next,07/13] flow_offload: add skip_hw and skip_sw to control if offload the action
    https://git.kernel.org/netdev/net-next/c/7adc57651211
  - [v8,net-next,08/13] flow_offload: rename exts stats update functions with hw
    https://git.kernel.org/netdev/net-next/c/bcd64368584b
  - [v8,net-next,09/13] flow_offload: add process to update action stats from hardware
    https://git.kernel.org/netdev/net-next/c/c7a66f8d8a94
  - [v8,net-next,10/13] net: sched: save full flags for tc action
    https://git.kernel.org/netdev/net-next/c/e8cb5bcf6ed6
  - [v8,net-next,11/13] flow_offload: add reoffload process to update hw_count
    https://git.kernel.org/netdev/net-next/c/13926d19a11e
  - [v8,net-next,12/13] flow_offload: validate flags of filter and actions
    https://git.kernel.org/netdev/net-next/c/c86e0209dc77
  - [v8,net-next,13/13] selftests: tc-testing: add action offload selftest for action and filter
    https://git.kernel.org/netdev/net-next/c/eb473bac4a4b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-12-19 14:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 18:16 [PATCH v8 net-next 00/13] allow user to offload tc action to net device Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 01/13] flow_offload: fill flags to action structure Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 02/13] flow_offload: reject to offload tc actions in offload drivers Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 03/13] flow_offload: add index to flow_action_entry structure Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 04/13] flow_offload: rename offload functions with offload instead of flow Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 05/13] flow_offload: add ops to tc_action_ops for flow action setup Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 06/13] flow_offload: allow user to offload tc action to net device Simon Horman
2021-12-20  8:48   ` Eric Dumazet
2021-12-20  9:32     ` Baowen Zheng
2021-12-23  6:34   ` [flow_offload] 28798f55fe: WARNING:suspicious_RCU_usage kernel test robot
2021-12-23  6:34     ` kernel test robot
2021-12-23  6:42     ` Baowen Zheng
2021-12-23  6:42     ` Baowen Zheng
2021-12-23  6:42       ` Baowen Zheng
2021-12-17 18:16 ` [PATCH v8 net-next 07/13] flow_offload: add skip_hw and skip_sw to control if offload the action Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 08/13] flow_offload: rename exts stats update functions with hw Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 09/13] flow_offload: add process to update action stats from hardware Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 10/13] net: sched: save full flags for tc action Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 11/13] flow_offload: add reoffload process to update hw_count Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 12/13] flow_offload: validate flags of filter and actions Simon Horman
2021-12-17 18:16 ` [PATCH v8 net-next 13/13] selftests: tc-testing: add action offload selftest for action and filter Simon Horman
2021-12-19 14:30 ` patchwork-bot+netdevbpf [this message]

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=163992421261.25478.13959206033604654129.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=baowen.zheng@corigine.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@nvidia.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=ozsh@nvidia.com \
    --cc=petrm@nvidia.com \
    --cc=roid@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=simon.horman@corigine.com \
    --cc=vivien.didelot@gmail.com \
    --cc=vladbu@nvidia.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=xiyou.wangcong@gmail.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.