From: Alex Markuze <alex@weka.io>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Demos at IDF conference using DDIO
Date: Sun, 28 Sep 2014 10:08:23 +0300 [thread overview]
Message-ID: <CAKfHP0U-gLcOux1Adynvn9uedSgVagPR-ToXCJiOm2qqECCocw@mail.gmail.com> (raw)
In-Reply-To: <20140925200939.GA3565@mhcomputing.net>
Even IF only the Demo is available it would be useful.
I assume the people behind the Demo are pert of this mailing list (Or
someone on the mailing list knows them).
It would be great if the demo was publicly available anywhere.
On Thu, Sep 25, 2014 at 11:09 PM, Matthew Hall <mhall@mhcomputing.net> wrote:
> On Thu, Sep 25, 2014 at 07:27:21PM +0000, Anjali Kulkarni wrote:
>> 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
>
> Indeed it would be best if this stuff were documented first, then demoed.
> Otherwise it's hard to get reliably reproducible results.
>
> In particular something which went all the way through the processing pipeline
> from Rx to Tx L1-L7.
>
> Matthew.
next prev parent reply other threads:[~2014-09-28 7:01 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
2014-09-25 20:09 ` Matthew Hall
2014-09-28 7:08 ` Alex Markuze [this message]
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=CAKfHP0U-gLcOux1Adynvn9uedSgVagPR-ToXCJiOm2qqECCocw@mail.gmail.com \
--to=alex@weka.io \
--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).