DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz@6wind.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	 "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Making space in mbuf data-structure
Date: Wed, 16 Jul 2014 14:32:54 +0200	[thread overview]
Message-ID: <53C670F6.8070007@6wind.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725821338121@IRSMSX105.ger.corp.intel.com>

Hi Konstantin,

On 07/15/2014 11:07 AM, Ananyev, Konstantin wrote:
>> As this change would impact the core of DPDK, I think it would be
>> interesting to list some representative use-cases in order to evaluate
>> the cost of each solution. This will also help for future modifications,
>> and could be included in a sort of non-regression test?
>>
>
> I think this is a very good idea.
> Let's create a list of such test-cases.
> Two obvious apps from our side would probably be:
> - test-pmd iofwd mode
> - l3fwd
> What else should we add here?

I agree that test-pmd iofwd is a good reference to track regressions
or analyze performance issues, but I'm not sure it's a real use-case.
To me, it's more important to ensure that l3fwd performance stay stable
compared to iofwd.

I think l3fwd is the most representative of a DPDK application.

Other use-case could include:
- virtualization, maybe using ovdk?
- ip fragmentation / reassembly
- an application that encapsulate or decapsulate in a tunnel

Regards,
Olivier

  reply	other threads:[~2014-07-16 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 23:38 Richardson, Bruce
2014-07-07 10:19 ` Olivier MATZ
2014-07-08  7:04   ` Zhang, Helin
2014-07-08  7:16     ` Ivan Boule
2014-07-08  7:37       ` Zhang, Helin
2014-07-15  9:07   ` Ananyev, Konstantin
2014-07-16 12:32     ` Olivier MATZ [this message]
2014-07-15  9:31 ` Ananyev, Konstantin
2014-07-15 18:07   ` Richardson, Bruce

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=53C670F6.8070007@6wind.com \
    --to=olivier.matz@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    /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).