From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: Appropriate DPDK data structures for TCP sockets Date: Sun, 22 Feb 2015 16:02:04 -0800 Message-ID: <20150222160204.20816910@urahara> References: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "" To: Matthew Hall Return-path: In-Reply-To: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Sat, 21 Feb 2015 16:38:45 -0800 Matthew Hall wrote: > So far I was using rte_hash, but it's single writer multi reader, which is eventually going to need some more complicated locking and probably run kind of slow. Also, I need some timer functions to delete dead sockets and so forth, and rte_hash doesn't have any iteration API. Use userspace RCU? or BSD RB_TREE The existing rte_hash is too limited for many use cases.