From: Anjali Kulkarni <anjali@juniper.net>
To: Matthew Hall <mhall@mhcomputing.net>,
Jeff Shaw <jeffrey.b.shaw@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Demos at IDF conference using DDIO
Date: Thu, 25 Sep 2014 19:27:21 +0000 [thread overview]
Message-ID: <D049B980.31EB8%anjali@juniper.net> (raw)
In-Reply-To: <20140925191820.GA3117@mhcomputing.net>
Actually, in the demo that I saw they had probably used as many of the
accelerations as possible to get the kind of rates they described. Even if
we could see (a documentation of) what all things they used in this
particular application, it would help.
>From my discussions, it seemed as if there were some specific lookup APIs
that they used to get better performance.
Anjali
On 9/25/14 12:18 PM, "Matthew Hall" <mhall@mhcomputing.net> wrote:
>On Thu, Sep 25, 2014 at 09:11:24AM -0700, Jeff Shaw wrote:
>> Intel(R) Data Direct I/O Technology (Intel(R) DDIO) is a feature
>>introduced
>> with the Intel(R) Xeon(R) processor E5 family.
>>
>> It has been around for several years and is available at least on all
>>Xeon
>> E5 processors. DDIO is part of the platform, so any DPDK version can
>>take
>> advantage of the feature. There are several papers and videos
>>available on
>> the Internet that can provide more details.
>
>One difficulty I run into with a lot of these Intel accelerations... each
>one
>is described as an atomic entity independent of all the other possible
>accelerations. Nobody explains how to take all of them together to make a
>complete high-speend low-latency packet processing solution from L1-L7.
>
>It'd be nice to see an architecture level view of DPDK, along with the
>accelerations one could / should apply at each level, so there's some
>kind of
>checklist you can follow to be sure you used everything you should where
>you
>should. Otherwise you'll miss some stuff and waste the features you paid
>for.
>
>Also, how is DDIO different from the previous DCA accelerations?
>
>Thanks,
>Matthew.
next prev parent reply other threads:[~2014-09-25 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 15:19 Anjali Kulkarni
2014-09-25 16:11 ` Jeff Shaw
2014-09-25 19:18 ` Matthew Hall
2014-09-25 19:27 ` Anjali Kulkarni [this message]
2014-09-25 20:09 ` Matthew Hall
2014-09-28 7:08 ` Alex Markuze
2014-09-28 19:22 ` Jayakumar, Muthurajan
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=D049B980.31EB8%anjali@juniper.net \
--to=anjali@juniper.net \
--cc=dev@dpdk.org \
--cc=jeffrey.b.shaw@intel.com \
--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).