DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Appropriate DPDK data structures for TCP sockets
Date: Sun, 22 Feb 2015 20:50:53 -0800	[thread overview]
Message-ID: <F543F60F-083D-4018-8387-062EAF8319D1@mhcomputing.net> (raw)
In-Reply-To: <20150222160204.20816910@urahara>


On Feb 22, 2015, at 4:02 PM, Stephen Hemminger <stephen@networkplumber.org> wrote:
> Use userspace RCU? or BSD RB_TREE

Thanks Stephen,

I think the RB_TREE stuff is single threaded mostly.

But user-space RCU looks quite good indeed, I didn't know somebody ported it out of the kernel. I'll check it out.

Matthew.

  reply	other threads:[~2015-02-23  4:50 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
2015-02-23  4:50   ` Matthew Hall [this message]
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=F543F60F-083D-4018-8387-062EAF8319D1@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).