From: Mauricio Vasquez <mauricio.vasquez@polito.it>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Jan Viktorin <viktorin@rehivetech.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
anatoly.burakov@intel.com, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] doc: announce ivshmem support removal
Date: Thu, 28 Jul 2016 17:23:34 +0200 [thread overview]
Message-ID: <064a4109-711b-8377-53aa-f6c25236bf09@polito.it> (raw)
In-Reply-To: <CAATJJ0K=7u0uj7ovmAb8bx7EkN0ACBpekke96_Zx69a5f6xNAg@mail.gmail.com>
Hello All,
Here in Politecnico di Torino we use the ivshmem technology from a
research point of view.
Our research efforts focus in optimizing the inter-Virtual Network
Function communication, currently we have implemented two versions of
our prototype, they are described in [1] and [2].
Unfortunately, we do not have the human resources to implement the
improvements that are necessary for ivshmem in DPDK, however we could
provide some feedback and testing for possible patches.
Best Regards,
Mauricio Vasquez.
[1]
https://www.researchgate.net/publication/305699120_Transparent_Optimization_of_Inter-Virtual_Network_Function_Communication_in_Open_vSwitch
[2]
https://www.researchgate.net/publication/305699122_A_Transparent_Highway_for_inter-Virtual_Network_Function_Communication_with_Open_vSwitch
On 07/28/2016 11:20 AM, Christian Ehrhardt wrote:
> Hi Thomas,
> just my two cents as Ubuntu DPDK maintainer (and part of the Debian Team
> that does the same).
> (It seems I can reuse that line for all posts about the deprecation notices
> :-) )
>
> While IVSHMEM was enabled (as it was the default) I never heard of any
> users of what we provided so far.
> But that is expected considering that not all qemu bits are landed either.
> Since it will follow the process of "deprecation notice -> grace period ->
> ABI bump" on removal, I think packaging and consuming applications should
> be fine.
>
> I'd agree to Hiroshi that, if really needed a clean re-implementation more
> properly separated from EAL likely is the best way to go.
>
> I think it is a good change to drop rather complex code in favor of
> stabilizing the main paths:
> Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
>
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
>
> On Wed, Jul 27, 2016 at 9:08 PM, Jan Viktorin <viktorin@rehivetech.com>
> wrote:
>
>> On Wed, 20 Jul 2016 18:35:46 +0200
>> Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
>>
>>> There was a prior call with an explanation of what needs to be done:
>>> http://dpdk.org/ml/archives/dev/2016-June/040844.html
>>> - Qemu patch upstreamed
>>> - IVSHMEM PCI device managed by a PCI driver
>>> - No DPDK objects (ring/mempool) allocated by EAL
>>>
>>> As nobody seems interested, it is time to remove this code which
>>> makes EAL improvements harder.
>>>
>>> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>>> Acked-by: David Marchand <david.marchand@6wind.com>
>>> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> Acked-by: Jan Viktorin <viktorin@rehivetech.com
>>
prev parent reply other threads:[~2016-07-28 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 16:35 [dpdk-dev] [PATCH] " Thomas Monjalon
2016-07-22 0:36 ` Hiroshi Shimamoto
2016-07-22 7:52 ` Thomas Monjalon
2016-07-27 8:38 ` David Marchand
2016-07-28 18:09 ` Thomas Monjalon
2016-07-27 16:12 ` [dpdk-dev] " Maxime Coquelin
2016-07-27 19:08 ` Jan Viktorin
2016-07-28 9:20 ` Christian Ehrhardt
2016-07-28 15:23 ` Mauricio Vasquez [this message]
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=064a4109-711b-8377-53aa-f6c25236bf09@polito.it \
--to=mauricio.vasquez@polito.it \
--cc=anatoly.burakov@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=viktorin@rehivetech.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).