DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Furong <WBAHACER@126.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why IVSHMEM was removed since 16.11 ?
Date: Tue, 8 Aug 2017 09:05:45 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E451236978226D763@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <2f4bdab7-9873-e293-26fd-36ef5f2d80a1@126.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Furong
> Sent: Tuesday, August 8, 2017 8:26 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Why IVSHMEM was removed since 16.11 ?
> 
> The release notes of dpdk-16.11 had shown that IVSHMEM was removed
> due to some design issues.
> 
> So, what are these issues?
> 
> Thanks!
> 

Hi Furong,

There were multiple issues involved. Biggest of all, it required a patch to QEMU that wasn't maintained and wasn't upstream (i.e. vanilla QEMU didn't work with DPDK's implementation of IVSHMEM support). Second, it was basically hacked in to EAL in order to support what it does [1], and the engineering effort to fix all of that isn't worth the benefit it would provide, as no one appeared to be using it heavily enough to object to its deprecation.

Hope this clears things up.

[1] http://dpdk.org/ml/archives/dev/2016-June/040844.html

Thanks,
Anatoly 

  reply	other threads:[~2017-08-08  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  7:26 Furong
2017-08-08  9:05 ` Burakov, Anatoly [this message]
2017-08-22  4:45 ` [dpdk-dev] Intel 82599ES send packets failed on dpdk-17.05.1 after traffic testing zimeiw
2017-08-22  7:49   ` Ferruh Yigit
2017-08-22  8:30     ` zimeiw
2017-08-22  9:31       ` Ferruh Yigit
     [not found]         ` <14690343.b423.15e099a0469.Coremail.zimeiw@163.com>
     [not found]           ` <dc62a140-5dd3-a899-eff9-034d76a85854@intel.com>
     [not found]             ` <61108f0.c31e.15e0a35ef85.Coremail.zimeiw@163.com>
     [not found]               ` <0f7d45a5-12de-85bd-59d2-da212298c7d2@intel.com>
     [not found]                 ` <1fb0a58e.cb3.15e0c93ac86.Coremail.zimeiw@163.com>
     [not found]                   ` <78c407d1.4448.15e0d8bd37f.Coremail.zimeiw@163.com>
     [not found]                     ` <a2eed349-ca31-2ba2-6458-7c701c02aa33@intel.com>
2017-08-23 11:47                       ` zimeiw

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=C6ECDF3AB251BE4894318F4E451236978226D763@IRSMSX109.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=WBAHACER@126.com \
    --cc=dev@dpdk.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 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).