From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Appropriate DPDK data structures for TCP sockets
Date: Sun, 22 Feb 2015 16:02:04 -0800 [thread overview]
Message-ID: <20150222160204.20816910@urahara> (raw)
In-Reply-To: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0@mhcomputing.net>
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.
next prev parent reply other threads:[~2015-02-23 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 0:38 Matthew Hall
2015-02-23 0:02 ` Stephen Hemminger [this message]
2015-02-23 4:50 ` Matthew Hall
2015-02-23 14:48 ` Matt Laswell
2015-02-23 21:16 ` Matthew Hall
2015-02-23 21:51 ` Avi Kivity
2015-03-13 6:41 ` Matthew Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150222160204.20816910@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).