From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: 小川泰文 <usufumu@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce ivshmem support removal
Date: Thu, 04 Aug 2016 19:18:46 +0200 [thread overview]
Message-ID: <1570561.Rujcl7qAGG@xps13> (raw)
In-Reply-To: <CAJfGiV8-wWaEdAYjQsNYLkhL=JvrELpkDc8KfJK_FcTU9FAx7Q@mail.gmail.com>
2016-08-04 17:00, 小川泰文:
> Hi Thomas,
>
> I'm going to develop a NFV based carrier system with SPP because it's able
> to chain VMs in high-performance and I think it might be the best solution
> for service function chaining. Without ivshmem, throuput between VMs is
> largely decreased. So we are not so happy if ivshmem is obsoleted.
We are not obsoleting IVSHMEM which is a QEMU feature.
We are just dropping the automatic allocation of DPDK objects in the guest
through IVSHMEM.
It is a weird design that nobody really wants to maintain/redesign.
If someone wants to do the required work or reimplement it differently,
it may be accepted.
> As you mentioned, we can use v16.07 but it's unwelcome situation for us and
> our possible users cannot gain of improvements from future version of DPDK.
> I'm appreciated if you kindly keep ivshmem to be maintained.
Nobody wants to really work on it. That's a fact, sorry.
> Or, is there
> any idea for high-performance inter-VM communication as ivshmem?
Yes you can implement an IVSHMEM driver in DPDK.
There was an attempt to do so which is also unmaintained:
http://dpdk.org/browse/old/memnic/
I think it would be a better approach than what exists currently.
next prev parent reply other threads:[~2016-08-04 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 8:00 小川泰文
2016-08-04 17:18 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-20 16:35 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
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=1570561.Rujcl7qAGG@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=usufumu@gmail.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).