pespin submitted this change.

View Change

Increase per PDR (F-TEID) hashtable size

In tunmap scenario there's usually 2 PDRs/local-F-TEIDs per session,
hence it makes sense to at least double the hashtable size with respect
to session hashtable. In here we actually multiply it by 2 twice since
this is actually global and not per peer, hence we account for multiple
peers.

Change-Id: I7ee3e875020d707c05e13ee70952174ca4daad30
---
M include/osmocom/upf/upf.h
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/osmocom/upf/upf.h b/include/osmocom/upf/upf.h
index 1e5d702..2f25c99 100644
--- a/include/osmocom/upf/upf.h
+++ b/include/osmocom/upf/upf.h
@@ -116,13 +116,13 @@
 		int priority_post;
 		uint32_t next_chain_id_state;
 		/* hashtable of (struct upf_nft_tun)->node_by_chain_id: */
-		DECLARE_HASHTABLE(nft_tun_by_chain_id, 10);
+		DECLARE_HASHTABLE(nft_tun_by_chain_id, 12);
 	} tunmap;
 
 	struct {
 		uint32_t next_local_teid_state;
 		/* hashtable of (struct pdr)->node_by_local_f_teid: */
-		DECLARE_HASHTABLE(pdrs_by_local_f_teid, 10);
+		DECLARE_HASHTABLE(pdrs_by_local_f_teid, 12);
 		uint16_t next_echo_seq_nr;
 	} gtp;
 

To view, visit change 39581. To unsubscribe, or for help writing mail filters, visit settings.