Public bug reported:

* Explain the feature
 
Assured connections are those connections which deemed of "higher quality" and 
less
like to expire than non-assured connections, as they passed some stricter rule 
(e.g
in udp reply + connection lasting more than 2 seconds). This feature
offloads only those connections.
 
 
* How to test
 
Create OVS bridge with 2 devices mlx5 rep devices.
Enable HW offload and configure regular connection tracking OpenFlow rules:
 
e.g:
    ovs-ofctl del-flows br-ovs
    ovs-ofctl add-flow br-ovs arp,actions=normal
    ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
    ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
    ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"
 
Run a short UDP connection (< 2 seconds), e.g:
on mlx5 VF1 iperf -s -u
on mlx5 VF2 iperf -c <ip> -t 1 -u 

Run longer UDP connection (> 2 seconds), e.g:
on mlx5 VF1 iperf -s -u
on mlx5 VF2 iperf -c <ip> -t 10 -u 

With the above commit quick lived UDP connections (< 2 seconds) will not be 
offloaded to the flow table
as can be checked by
cat /proc/net/nf_conntrack | grep -i offload
while connections lasting more than 2 seconds (and of course double sided) will 
be offloaded.
 
* What it could break.
 
NA

** Affects: linux-bluefield (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1961819

Title:
  CT: Offload only ASSURED connections

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the feature
   
  Assured connections are those connections which deemed of "higher quality" 
and less
  like to expire than non-assured connections, as they passed some stricter 
rule (e.g
  in udp reply + connection lasting more than 2 seconds). This feature
  offloads only those connections.
   
   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.
  Enable HW offload and configure regular connection tracking OpenFlow rules:
   
  e.g:
      ovs-ofctl del-flows br-ovs
      ovs-ofctl add-flow br-ovs arp,actions=normal
      ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
      ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
      ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"
   
  Run a short UDP connection (< 2 seconds), e.g:
  on mlx5 VF1 iperf -s -u
  on mlx5 VF2 iperf -c <ip> -t 1 -u 

  Run longer UDP connection (> 2 seconds), e.g:
  on mlx5 VF1 iperf -s -u
  on mlx5 VF2 iperf -c <ip> -t 10 -u 

  With the above commit quick lived UDP connections (< 2 seconds) will not be 
offloaded to the flow table
  as can be checked by
  cat /proc/net/nf_conntrack | grep -i offload
  while connections lasting more than 2 seconds (and of course double sided) 
will be offloaded.
   
  * What it could break.
   
  NA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1961819/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to