net: Pass full skb hash to ndo_rx_flow_steer
Subsystems (2)
RFC PATCH 1/1 net: Pass full skb hash to ndo_rx_flow_steer
Currently, for aRFS the index into the flow table is passed to ndo_rx_flow_steer as the flow ID of a connection. This is the skb->hash & the table mask. It looks like the backend can accept the full skb->hash as the flow ID which should reduce the number of collisions in the hardware tables.
This patch provides the skb->hash to the driver for flow steering. Expiration of HW steered flows was also updated.
With a hash collision in RFS, ndo_rx_flow_steer will continue to be called with different CPUs, but now with different flow_ids. If this is still too much device interaction, then it might make sense for the driver to do its own lookup in its structure to see if a matching filter is already installed for a given flow_id, an if it is just refresh a timestamp to avoid expiration (based on looking at sfc driver).
I don't currently have any HW to test this, if someone could try this on hardware with aRFS and provide feedback that would be appreciated.
--- net/core/dev.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
net/core/dev.c +4 -3
@@ -3057,7 +3057,8 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb, goto out; flow_id =skb_get_hash (skb) & flow_table->mask; rc = dev->netdev_ops->ndo_rx_flow_steer (dev, skb, - rxq_index, flow_id); + rxq_index, +skb_get_hash (skb));if (rc <0 ) goto out; old_rflow = rflow;
@@ -3195,8 +3196,8 @@ bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index,rcu_read_lock (); flow_table =rcu_dereference (rxqueue->rps_flow_table); -if (flow_table && flow_id <= flow_table->mask) { - rflow = &flow_table->flows[flow_id]; +if (flow_table) { + rflow = &flow_table->flows[flow_id & flow_table->mask]; cpu =ACCESS_ONCE (rflow->cpu); if (rflow->filter == filter_id && cpu != RPS_NO_CPU && ((int)(per_cpu(softnet_data, cpu).input_queue_head -
Signature · 1 line
2.1.0.rc2.206.gedb03e5
David Miller
maintainerFrom: Tom Herbert <[email protected]>
Date: Tue, 18 Nov 2014 20:08:57 -0800
Quoted 17 lines
Currently, for aRFS the index into the flow table is passed to
ndo_rx_flow_steeras the flow ID of a connection. This is theskb->hash& the table mask. It looks like the backend can accept the fullskb->hashas the flow ID which should reduce the number of collisions in the hardware tables.This patch provides the
skb->hashto the driver for flow steering. Expiration of HW steered flows was also updated.With a hash collision in RFS,
ndo_rx_flow_steerwill continue to be called with different CPUs, but now with differentflow_ids. If this is still too much device interaction, then it might make sense for the driver to do its own lookup in its structure to see if a matching filter is already installed for a givenflow_id, an if it is just refresh a timestamp to avoid expiration (based on looking at sfc driver).
Quoted 4 lines
I don't currently have any HW to test this, if someone could try this on hardware with aRFS and provide feedback that would be appreciated.
Signed-off-by Tom Herbert <[email protected]>
This seems legitimate to me.
The only thing a driver can reliably do with the flow_id is pass it back into rps_may_expire_flow(). Therefore you can pass it in whatever format you like.
Quoted 30 lines · Tom Herbert
Currently, for aRFS the index into the flow table is passed to
ndo_rx_flow_steeras the flow ID of a connection. This is theskb->hash& the table mask. It looks like the backend can accept the fullskb->hashas the flow ID which should reduce the number of collisions in the hardware tables.This patch provides the
skb->hashto the driver for flow steering. Expiration of HW steered flows was also updated.With a hash collision in RFS,
ndo_rx_flow_steerwill continue to be called with different CPUs, but now with differentflow_ids. If this is still too much device interaction, then it might make sense for the driver to do its own lookup in its structure to see if a matching filter is already installed for a givenflow_id, an if it is just refresh a timestamp to avoid expiration (based on looking at sfc driver).I don't currently have any HW to test this, if someone could try this on hardware with aRFS and provide feedback that would be appreciated.
Signed-off-by Tom Herbert <[email protected]>--- net/core/dev.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)net/core/dev.c +0
-0
net/core/dev.c set_rps_cpu(struct net_device *dev, struct sk_buff *skb, · line 3061
Quoted 6 lines
net/core/dev.c +2
-1@@ -3057,7 +3057,8 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb, goto out; flow_id =skb_get_hash (skb) & flow_table->mask; rc = dev->netdev_ops->ndo_rx_flow_steer (dev, skb, - rxq_index, flow_id); + rxq_index, +skb_get_hash (skb));
Can gcc CSE this? Not that it matters that much.
net/core/dev.c bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index, · line 3200
Quoted 11 lines
net/core/dev.c +2
-2if (rc <0 ) goto out; old_rflow = rflow;@@ -3195,8 +3196,8 @@ bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index,rcu_read_lock (); flow_table =rcu_dereference (rxqueue->rps_flow_table); -if (flow_table && flow_id <= flow_table->mask) { - rflow = &flow_table->flows[flow_id]; +if (flow_table) { + rflow = &flow_table->flows[flow_id & flow_table->mask];
I think this is nicer, but why will it help? If there's a collision in the low bits of the hash, we'll still think that the flow is expired.
Is there a real LRU-ish hash table that could be subbed in easily? There ought to be a data structure that's barely more complicated than this kind of hash table but that gives much better behavior when the number of flows is smaller than the table size.
--Andy
Quoted 6 lines
net/core/dev.c +0
-1cpu =ACCESS_ONCE (rflow->cpu); if (rflow->filter == filter_id && cpu != RPS_NO_CPU && ((int)(per_cpu(softnet_data, cpu).input_queue_head - --2.1.0.rc2.206.gedb03e5
Signature · 2 lines
Andy Lutomirski AMA Capital Management, LLC
Quoted 56 lines · Andy Lutomirski
Quoted 30 lines · Tom Herbert
Currently, for aRFS the index into the flow table is passed to
ndo_rx_flow_steeras the flow ID of a connection. This is theskb->hash& the table mask. It looks like the backend can accept the fullskb->hashas the flow ID which should reduce the number of collisions in the hardware tables.This patch provides the
skb->hashto the driver for flow steering. Expiration of HW steered flows was also updated.With a hash collision in RFS,
ndo_rx_flow_steerwill continue to be called with different CPUs, but now with differentflow_ids. If this is still too much device interaction, then it might make sense for the driver to do its own lookup in its structure to see if a matching filter is already installed for a givenflow_id, an if it is just refresh a timestamp to avoid expiration (based on looking at sfc driver).I don't currently have any HW to test this, if someone could try this on hardware with aRFS and provide feedback that would be appreciated.
Signed-off-by Tom Herbert <[email protected]>--- net/core/dev.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)net/core/dev.c +0
-0net/core/dev.c set_rps_cpu(struct net_device *dev, struct sk_buff *skb, · line 3061
Quoted 6 lines
net/core/dev.c +2
-1@@ -3057,7 +3057,8 @@ set_rps_cpu(struct net_device *dev, struct sk_buff *skb, goto out; flow_id =skb_get_hash (skb) & flow_table->mask; rc = dev->netdev_ops->ndo_rx_flow_steer (dev, skb, - rxq_index, flow_id); + rxq_index, +skb_get_hash (skb));Can gcc CSE this? Not that it matters that much.
net/core/dev.c bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index, · line 3200
Quoted 11 lines
net/core/dev.c +2
-2if (rc <0 ) goto out; old_rflow = rflow;@@ -3195,8 +3196,8 @@ bool rps_may_expire_flow(struct net_device *dev, u16 rxq_index,rcu_read_lock (); flow_table =rcu_dereference (rxqueue->rps_flow_table); -if (flow_table && flow_id <= flow_table->mask) { - rflow = &flow_table->flows[flow_id]; +if (flow_table) { + rflow = &flow_table->flows[flow_id & flow_table->mask];I think this is nicer, but why will it help? If there's a collision in the low bits of the hash, we'll still think that the flow is expired.
Quoted 1 line
Is there a real LRU-ish hash table that could be subbed in easily?
I think this does exist in sfc, or at least could potentially be updated to do it. When a filter is being inserted, there is a lookup on the spec to see if a matching filter already exists. If it is found, -EBUSY is returned. I "think" that instead of returning -EBUSY, the filter index could be returned and a timestamp in the soft data structure could be refreshed. In the driver expiration code, the timestamp could be checked before deciding to call rps_may_expire_flow. In the case of a collision in the RPS flow table, ndo_rx_flow_steer would be alternately called for the flows which should continuously refresh the timestamps of the filters for each flow. This should keep both flow filters active in the device, without needing to whack the device for each call to ndo_rx_flow_steer.
Quoted 18 lines
There ought to be a data structure that's barely more complicated than this kind of hash table but that gives much better behavior when the number of flows is smaller than the table size.
--Andy
Quoted 6 lines
net/core/dev.c +0
-1cpu =ACCESS_ONCE (rflow->cpu); if (rflow->filter == filter_id && cpu != RPS_NO_CPU && ((int)(per_cpu(softnet_data, cpu).input_queue_head - --2.1.0.rc2.206.gedb03e5
--
Andy Lutomirski
AMA Capital Management, LLC