[dpdk-dev] [PATCH v3] rte_hash: add scalable multi-writer insertion w/ Intel TSX

2016-06-16 Thread Wei Shen
This patch introduced scalable multi-writer Cuckoo Hash insertion based on a split Cuckoo Search and Move operation using Intel TSX. It can do scalable hash insertion with 22 cores with little performance loss and negligible TSX abortion rate. * Added an extra rte_hash flag definition to switch de

[dpdk-dev] [PATCH v3] rte_hash: add scalable multi-writer insertion w/ Intel TSX

2016-06-16 Thread Wei Shen
ould cause problem when key deletion happens. Wei Shen (1): rte_hash: add scalable multi-writer insertion w/ Intel TSX app/test/Makefile | 1 + app/test/test_hash_multiwriter.c | 287 + doc/guides/rel_notes/release_16_07.rst |

[dpdk-dev] [PATCH v2] rte_hash: add scalable multi-writer insertion w/ Intel TSX

2016-06-15 Thread Wei Shen
This patch introduced scalable multi-writer Cuckoo Hash insertion based on a split Cuckoo Search and Move operation using Intel TSX. It can do scalable hash insertion with 22 cores with little performance loss and negligible TSX abortion rate. * Added an extra rte_hash flag definition to switch de

[dpdk-dev] Order of system brought up affects throughput with qos_sched app

2015-09-09 Thread Wei Shen
r > normal values (this time can actually be comuted/estimated). > > If this is what happens in your case, lowering the size of your buckets will > help. > > Regards, > Cristian > > > -----Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Be

[dpdk-dev] Order of system brought up affects throughput with qos_sched app

2015-09-09 Thread Wei Shen
tried to assign qos_sched on different cores and got the same result. I suspect that there is some rte_ring bugs when connecting two cores and one core started enqueuing before another core is ready for dequeue. Have you experienced the same issue? Appreciate your help. Wei Shen