From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-ig0-f172.google.com (mail-ig0-f172.google.com
 [209.85.213.172]) by dpdk.org (Postfix) with ESMTP id 2665AADC0
 for <dev@dpdk.org>; Mon, 23 Feb 2015 01:02:03 +0100 (CET)
Received: by mail-ig0-f172.google.com with SMTP id l13so14597205iga.5
 for <dev@dpdk.org>; Sun, 22 Feb 2015 16:02:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=Imf5x9MDbcTObwvfh4hkSMBFfPwfOWFRW0tJYJJvYf8=;
 b=hrDMmcm5xbq1YwjrqDHM6uxaUu6M6vzBMmwtNwvycB1dfyVgzcnEbgwqECdHPc1qe1
 1ftp/MkGuBeYxaJXEfkXCHDn6obVPzRlh2n4lQqdBVHllgYujmDFDZKUszdWpTCHhpJY
 oUunWL9NSGhi1sWLGFXUmf5WgQH7VNEroD+ZTa8lfx3eaco71SVhKztkkYSdrWXWzpq3
 Q48VctM2jsPhVMOgnbhaDmg0VZF0zT5H/G3Klgfj1vIt4juRL72uPebaoyBfxojLQaf5
 U7uXHawM+sumoT3VtcWeC8GLa3s0xhadDsKnyDaDOAppXyvsUyzmRTz7LPkk+Zlf81Vw
 On5A==
X-Gm-Message-State: ALoCoQla5xpXHzaJRCL2CDh0JvjVBQmWmgEC2gpKk2H2ZhxIf2cDUNjj2nJwt/1rHvYzhhg2Cj4C
X-Received: by 10.107.40.2 with SMTP id o2mr10748912ioo.68.1424649722208;
 Sun, 22 Feb 2015 16:02:02 -0800 (PST)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by mx.google.com with ESMTPSA id 76sm5514750iom.29.2015.02.22.16.02.01
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sun, 22 Feb 2015 16:02:02 -0800 (PST)
Date: Sun, 22 Feb 2015 16:02:04 -0800
From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Message-ID: <20150222160204.20816910@urahara>
In-Reply-To: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0@mhcomputing.net>
References: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0@mhcomputing.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Appropriate DPDK data structures for TCP sockets
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Feb 2015 00:02:03 -0000

On Sat, 21 Feb 2015 16:38:45 -0800
Matthew Hall <mhall@mhcomputing.net> 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.