From: Matthew Hall <mhall@mhcomputing.net>
To: Avi Kivity <avi@cloudius-systems.com>
Cc: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Appropriate DPDK data structures for TCP sockets
Date: Thu, 12 Mar 2015 23:41:03 -0700 [thread overview]
Message-ID: <20150313064103.GA9389@mhcomputing.net> (raw)
In-Reply-To: <54EBA0F2.6040409@cloudius-systems.com>
On Mon, Feb 23, 2015 at 11:51:46PM +0200, Avi Kivity wrote:
> https://github.com/cloudius-systems/seastar
Hi Avi and others,
My code unintentionally ended up looking somewhat like a C version of your
seastar C++ code, even though I didn't really look at yours too much when I
coded mine as it was using a lot of hardcore C++ features I really don't have
any clue about. :)
Someday maybe we can all do a bake-off of tests of DPDK TCPs and Host TCPs and
see what kind of stability, features, and performance we can get.
I didn't use anything too crazy or high performance just yet... just rte_hash
and some spinlocks... but I'm keeping all the collective advice in mind to
figure out how I'm going to make all this stuff work right soon.
Matthew.
prev parent reply other threads:[~2015-03-13 6:41 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
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 [this message]
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=20150313064103.GA9389@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=avi@cloudius-systems.com \
--cc=dev@dpdk.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).