From: Thomas Monjalon <thomas@monjalon.net>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/5] allow procinfo and pdump on eth vdev
Date: Fri, 13 Apr 2018 01:30:45 +0200 [thread overview]
Message-ID: <1561788.jEzySPKPAF@xps> (raw)
In-Reply-To: <1522950303-17206-1-git-send-email-jianfeng.tan@intel.com>
Hi Jinafeng,
05/04/2018 19:44, Jianfeng Tan:
> As we know, we have below limitations in vdev:
> - dpdk-procinfo cannot get the stats of (most) vdev in primary process;
> - dpdk-pdump cannot dump the packets for (most) vdev in primary proces;
> - secondary process cannot use (most) vdev in primary process.
>
> The very first reason is that the secondary process actually does not know
> the existence of those vdevs as vdevs are chained on a linked list, and
> not shareable to secondary.
>
> In this patch series, we would like to propose a vdev sharing model like this:
> - As a secondary process boots, all devices (including vdev) in primary
> will be automatically shared. After both primary and secondary process
> booted,
> - Device add/remove in primary will be translated to device hog plug/unplug
> event in secondary processes. (TODO)
> - Device add in secondary
> * If that kind of device support multi-process, the secondary will
> request the primary to probe the device and the primary to share
> it to the secondary. It's not necessary to have secondary-private
> device in this case. (TODO)
> * If that kind of device does not support multi-process, the secondary
> will probe the device by itself, and the port id is shared among
> all primary/secondary processes.
Are you OK to consider this series for DPDK 18.08?
next prev parent reply other threads:[~2018-04-12 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 17:44 [PATCH v2 0/5] allow procinfo and pdump on eth vdev Jianfeng Tan
2018-04-05 17:44 ` [PATCH v2 1/5] eal: bring forward multi-process channel init Jianfeng Tan
2018-04-05 17:45 ` [PATCH v2 2/5] bus/vdev: add lock on vdev device list Jianfeng Tan
2018-04-05 17:45 ` [PATCH v2 3/5] bus/vdev: bus scan by multi-process channel Jianfeng Tan
2018-04-05 17:45 ` [PATCH v2 4/5] drivers/net: not use private eth dev data Jianfeng Tan
2018-04-05 17:45 ` [PATCH v2 5/5] drivers/net: share vdev data to secondary process Jianfeng Tan
2018-04-12 23:30 ` Thomas Monjalon [this message]
2018-04-13 14:39 ` [PATCH v2 0/5] allow procinfo and pdump on eth vdev Tan, Jianfeng
2018-04-17 2:24 ` Zhang, Qi Z
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=1561788.jEzySPKPAF@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.