From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: "anatoly.burakov@intel.com" <anatoly.burakov@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce ivshmem support removal
Date: Fri, 22 Jul 2016 00:52:01 -0700 (PDT) [thread overview]
Message-ID: <1627928.Urc8at9buT@xps13> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD0602E280@BPXM14GP.gisp.nec.co.jp>
2016-07-22 00:36, Hiroshi Shimamoto:
> Hi,
>
> > Subject: [dpdk-dev] [PATCH] doc: announce ivshmem support removal
> >
> > 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.
>
> I'd like to confirm about the issue.
> I know there are real users who rely on ivshmem mechanism. e.g. spp user.
> Unfortunately they don't prefer to expose their opinion to the community.
> Furthermore they may not have noticed this situation.
These secret users can use the version 16.07.
> Anyway, it is the issue that the current ivshmem implementation breaks
> EAL framework and is much complicated, right?
> IIUC, for DPDK, ivshmem support module should be separated from a middle of
> EAL code and make it as a PCI driver. That means the current rte_ivshmem
> removal should happen. To keep the functionality to share DPDK objects
> between host and guest in shared memory like ivshmem, it should be
> implemented cleanly.
> Is my understanding correct?
Yes
You just forgot the need for a patch on Qemu.
next prev parent reply other threads:[~2016-07-22 7:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 16:35 Thomas Monjalon
2016-07-22 0:36 ` Hiroshi Shimamoto
2016-07-22 7:52 ` Thomas Monjalon [this message]
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
2016-08-04 8:00 [dpdk-dev] [PATCH] " 小川泰文
2016-08-04 17:18 ` 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=1627928.Urc8at9buT@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=h-shimamoto@ct.jp.nec.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).