Message ID | 1581847296-19194-1-git-send-email-paulb@mellanox.com |
---|---|
Headers | show |
Series | Handle multi chain hardware misses | expand |
On Sun, 2020-02-16 at 12:01 +0200, Paul Blakey wrote: > Hi David/Jakub/Saeed, > > TC multi chain configuration can cause offloaded tc chains to miss in > hardware after jumping to some chain. In such cases the software > should > continue from the chain that was missed in hardware, as the hardware > may have > manipulated the packet and updated some counters. > [...] > Note that miss path handling of multi-chain rules is a required > infrastructure > for connection tracking hardware offload. The connection tracking > offload > series will follow this one. > Hi Dave, As was agreed, i will apply this series and the two to follow to a side branch until all the connection tracking offloads patchsets are posted by Paul and reviewed/acked. in case of no objection i will apply this patchset to allow Paul to move forward with the other two connection tracking patchsets. Thanks, Saeed.
From: Saeed Mahameed <saeedm@mellanox.com> Date: Wed, 19 Feb 2020 02:43:08 +0000 > On Sun, 2020-02-16 at 12:01 +0200, Paul Blakey wrote: >> Hi David/Jakub/Saeed, >> >> TC multi chain configuration can cause offloaded tc chains to miss in >> hardware after jumping to some chain. In such cases the software >> should >> continue from the chain that was missed in hardware, as the hardware >> may have >> manipulated the packet and updated some counters. >> > > [...] > >> Note that miss path handling of multi-chain rules is a required >> infrastructure >> for connection tracking hardware offload. The connection tracking >> offload >> series will follow this one. >> > > Hi Dave, > > As was agreed, i will apply this series and the two to follow to a side > branch until all the connection tracking offloads patchsets are posted > by Paul and reviewed/acked. > > in case of no objection i will apply this patchset to allow Paul to > move forward with the other two connection tracking patchsets. I have no objection to this series, can you setup a pull request with this series in it that I can pull from into net-next? Thanks.
On Wed, 2020-02-19 at 16:12 -0800, David Miller wrote: > From: Saeed Mahameed <saeedm@mellanox.com> > Date: Wed, 19 Feb 2020 02:43:08 +0000 > > > On Sun, 2020-02-16 at 12:01 +0200, Paul Blakey wrote: > >> Hi David/Jakub/Saeed, > >> > >> TC multi chain configuration can cause offloaded tc chains to miss > in > >> hardware after jumping to some chain. In such cases the software > >> should > >> continue from the chain that was missed in hardware, as the > hardware > >> may have > >> manipulated the packet and updated some counters. > >> > > > > [...] > > > >> Note that miss path handling of multi-chain rules is a required > >> infrastructure > >> for connection tracking hardware offload. The connection tracking > >> offload > >> series will follow this one. > >> > > > > Hi Dave, > > > > As was agreed, i will apply this series and the two to follow to a > side > > branch until all the connection tracking offloads patchsets are > posted > > by Paul and reviewed/acked. > > > > in case of no objection i will apply this patchset to allow Paul to > > move forward with the other two connection tracking patchsets. > > I have no objection to this series, can you setup a pull request with > this > series in it that I can pull from into net-next? > Great, Yes i will setup the pull request. Series applied to ct-offload branch: https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/log/?h=ct-offload I will send the pull request once all connection tracking offload patches are posted and reviewed in net-next. Thanks.