From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
David Marchand <david.marchand@6wind.com>,
dev@dpdk.org, sergio.gonzalez.monroy@intel.com,
kevin.traynor@intel.com, pmatilai@redhat.com
Subject: Re: [dpdk-dev] [PATCH] dropping librte_ivshmem
Date: Mon, 20 Jun 2016 16:44:59 +0100 [thread overview]
Message-ID: <57680F7B.5040104@intel.com> (raw)
In-Reply-To: <2195337.EI94ugUIUk@xps13>
On 6/15/2016 7:34 PM, Thomas Monjalon wrote:
> 2016-06-15 19:16, Ferruh Yigit:
>> On 6/9/2016 10:26 PM, Thomas Monjalon wrote:
>>> So this is my proposal:
>>> Someone start working on the above cleanup now, otherwise the whole
>>> rte_ivshmem feature will be deprecated in 16.07 and removed in 16.11.
>>
>> I would like to note that at least SPP (soft patch panel) is using
>> rte_ivshmem feature.
>
> Why?
> Can SPP work without ivshmem?
>
Can do, it supports both ivshmem and vhost.
But ivshmem gives clearly more performance for VM to VM communication.
next prev parent reply other threads:[~2016-06-20 15:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 14:09 [dpdk-dev] [PATCH] log: deprecate history dump Thomas Monjalon
2016-06-09 14:45 ` David Marchand
2016-06-09 15:01 ` Thomas Monjalon
2016-06-09 21:26 ` [dpdk-dev] [PATCH] dropping librte_ivshmem - was " Thomas Monjalon
2016-06-10 9:05 ` Burakov, Anatoly
2016-06-10 9:30 ` Thomas Monjalon
2016-06-10 9:47 ` Burakov, Anatoly
2016-06-10 10:13 ` Thomas Monjalon
2016-06-10 12:08 ` Burakov, Anatoly
2016-06-10 12:26 ` Thomas Monjalon
2016-06-15 18:16 ` Ferruh Yigit
2016-06-15 18:34 ` [dpdk-dev] [PATCH] dropping librte_ivshmem Thomas Monjalon
2016-06-20 15:44 ` Ferruh Yigit [this message]
2016-06-20 15:54 ` Thomas Monjalon
2016-06-21 6:49 ` [dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump Panu Matilainen
2016-06-09 15:01 ` [dpdk-dev] [PATCH] " Christian Ehrhardt
2016-06-09 15:06 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2016-06-09 22:10 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2016-06-10 9:50 ` David Marchand
2016-06-10 13:09 ` Thomas Monjalon
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=57680F7B.5040104@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=kevin.traynor@intel.com \
--cc=pmatilai@redhat.com \
--cc=sergio.gonzalez.monroy@intel.com \
--cc=thomas.monjalon@6wind.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).