All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier MATZ <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Ananyev,
	Konstantin"
	<konstantin.ananyev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"Richardson,
	Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"dev-VfR2kkLFssw@public.gmane.org"
	<dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: 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-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>

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

  parent 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 Making space in mbuf data-structure Richardson, Bruce
     [not found] ` <59AF69C657FD0841A61C55336867B5B02CF13E32-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-07-07 10:19   ` Olivier MATZ
     [not found]     ` <53BA7422.9080706-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-07-08  7:04       ` Zhang, Helin
     [not found]         ` <F35DEAC7BCE34641BA9FAC6BCA4A12E70A74B3F6-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-07-08  7:16           ` Ivan Boule
     [not found]             ` <53BB9AE6.4030503-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-07-08  7:37               ` Zhang, Helin
2014-07-15  9:07       ` Ananyev, Konstantin
     [not found]         ` <2601191342CEEE43887BDE71AB97725821338121-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-07-16 12:32           ` Olivier MATZ [this message]
2014-07-15  9:31   ` Ananyev, Konstantin
     [not found]     ` <2601191342CEEE43887BDE71AB97725821338148-kPTMFJFq+rEu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=konstantin.ananyev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.