From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f170.google.com (mail-wr0-f170.google.com [209.85.128.170]) by dpdk.org (Postfix) with ESMTP id 7BF07968 for ; Mon, 26 Jun 2017 02:22:25 +0200 (CEST) Received: by mail-wr0-f170.google.com with SMTP id c11so131613188wrc.3 for ; Sun, 25 Jun 2017 17:22:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id; bh=ifdU3lLtQBfjougvpQj//w2ZcJ2chG6Wp2S1dNby8S0=; b=kn1JM41lRqKHsiMh0y8w+OeBnNO53FFlzY/a2t8ta8HHj3uc5iW9j7fWkkEoJwWuec dRBzURLwSYGPAgQrXFkWgKMW7s6thI84sN3Wv6IuUCEWcBehDh0lCQMbEmFxWpy/V1M7 79NJBUJ9lJ85D6UTnLnDDnF92q/ru/Lkm7Ik8qcEMkcTPJDOLR1aHw7E/4ZTqm6rU+yE LFiMmAc3BRYFObNoqXVCaFcCQyVXop7TkHSOQgo0RSTNLkSh0G2TP3NFXwtseo/lLZf3 HiyQpGxjoEEnJm4pztsyABvDHictXB4Nw6TRJOgUpeHPSzERsulZLk/ZbJBOd+b2w7a7 X97w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=ifdU3lLtQBfjougvpQj//w2ZcJ2chG6Wp2S1dNby8S0=; b=GmtSlHULUiGQITbCmARl+AgyWV7I2O+cyXksIDQg9pHtkMzVzOOTUDN04eLs5ysJUv gFadrTdTi/LjYGZbygeZECYjfdq5Wfjj7QYVKuSJXhYZslN7nRjThWfIp5nwh6vszfL5 /5lSRd5ihiNNTSymejjla/ofmaVJciAovmf6o5rWApMSKxfmY/Dg/39LZKlZprPzc0hp nfEwOyjJAEKobxRZWjYOK87XeILjIiFblQUY+bldzFZjQOypucBbQkTqm+9Xt4tbBwyP 2S70cm36JxX43LBjc7+lOep49yBv9cNDc+L6bBCSDUCUGZ8d1KcMcW3sj6uIgRta911f bJBA== X-Gm-Message-State: AKS2vOzdhxZZtQP4fQDJhPv1MECoHEcV+zVDlnjYFZpIfrFRTsR5JFr1 IH9hjMuL/ixCIOKAGd4= X-Received: by 10.223.128.209 with SMTP id 75mr6757728wrl.99.1498436544727; Sun, 25 Jun 2017 17:22:24 -0700 (PDT) Received: from bidouze.dev.6wind.com ([62.23.145.78]) by smtp.gmail.com with ESMTPSA id 19sm16061626wrx.26.2017.06.25.17.22.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 25 Jun 2017 17:22:23 -0700 (PDT) From: Gaetan Rivet To: dev@dpdk.org Cc: Gaetan Rivet , Jan Blunck , Shreyansh Jain , Stephen Hemminger Date: Mon, 26 Jun 2017 02:21:58 +0200 Message-Id: X-Mailer: git-send-email 2.1.4 Subject: [dpdk-dev] [PATCH v5 00/12] bus: attach / detach API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jun 2017 00:22:25 -0000 Following the work from Jan: This patchset introduces the attach / detach API to rte_bus. The rte_device structure is used as the generic device representation. This API is implemented for the virtual bus. The functions rte_eal_dev_attach and rte_eal_dev_detach are updated to use this new interface. -- v2 0. API rework ------------- I would like to propose an evolution on the API developed by Jan. The attach / detach rte_bus API is necessary to support the attach/detach rte_dev API. Those are two different levels for one similar functionality. Attach / detach does not allow true hotplugging, because the attach function expects the devices operated upon to already exist within the buses / sub-layers. This means that this API expects devices meta-datas (bus-internal device representation and associated device information read from the system) to be present upon attach. This part of the work is done during scanning. While it is best to avoid changing the public rte_dev API as it already exists, nothing prevents this new rte_bus API from superseeding it. It has been said during the previous release cycle that device hotplug was a feature that interested users. True hotplug is not allowed by the current attach / detach API. Worse, this API hinders the effort to bring this new functionality by squatting its semantic field. Thus, I propose to rename rte_bus attach / detach; plug / unplug. As it is a superset of the attach / detach functionality, it can be used to implement rte_dev attach / detach. Now is the right time to pivot to this new feature. This should help maintainers understanding the aim of this API and the differences with the APIs higher-up, clarify the field and allow a new functionality to be proposed. The vdev bus is inherently supporting the new API, however it has been made explicit. My implementation in the PCI bus in further patchset also follows the rte_bus hotplug API instead of only attach / detach. One remaining problem with the vdev bus is the rte_dev attach implementation, which needs the rte_devargs rework to be properly fixed. 1. Additional evolutions in the patchset ---------------------------------------- The RTE_VERIFY on the find_device is too stringent I think and forces all buses to implement a public device iterator. While it could be argued that it would push for quicker support for the functionality, I think it's possible that some buses are not interested at all in it and should simply be ignored. The bus devices iterator has been fixed. The internal rte_device handle was not properly setup within the net_ring PMD. -- v3 The new API is now typedef struct rte_device * (*rte_bus_plug_t)(struct rte_devargs *da); typedef int (*rte_bus_unplug_t)(struct rte_device *dev); So, plugging a device takes an rte_devargs as input and returns an rte_device. While implementing related subsystems, I found that I usually needed this rte_device handle upon a successful device plugging. This seems the sensible and useful thing to do. As such, on error NULL is returned and rte_errno is set by the bus. Unplugging a device however now returns to the first version, which used an rte_device. The explicit contract here is that if one has an rte_device that has been obtained by calling bus->plug(), then this handle can be used for bus->unplug(). Additionally, bus and device comparators now returns 0 on match, following strcmp-like behavior. -- v4 * rte_bus_find now takes a *start* parameter, that can be null. The bus search starts from this element if set. * A few doc fixes. * The rte_device field was fixed within the rte_ring PMD in a previous patch. This fix has been integrated by other means, it is not necessary anymore. -- v5 * The commit ethdev: use embedded rte_device to detach driver has been removed from this series to be sent separately. * The PCI support for device access and hotplug is merged in this series instead of being proposed as a separate patchset. * A few nitpicks to the code itself have been fixed. * Some documentation has been reworked. Gaetan Rivet (5): vdev: implement hotplug functionality vdev: expose bus name vdev: use standard bus registration function pci: implement find_device bus operation pci: implement hotplug bus operation Jan Blunck (7): bus: add bus iterator to find a bus bus: add device iterator method bus: add helper to find which bus holds a device bus: add bus iterator to find a device bus: introduce hotplug functionality vdev: implement find_device bus operation eal: make virtual driver probe and remove take rte_vdev_device lib/librte_eal/bsdapp/eal/rte_eal_version.map | 3 + lib/librte_eal/common/eal_common_bus.c | 71 ++++++++++++++ lib/librte_eal/common/eal_common_dev.c | 93 +++++++++++++----- lib/librte_eal/common/eal_common_pci.c | 57 +++++++++++ lib/librte_eal/common/eal_common_vdev.c | 65 ++++++++++--- lib/librte_eal/common/include/rte_bus.h | 124 ++++++++++++++++++++++++ lib/librte_eal/common/include/rte_dev.h | 21 ++++ lib/librte_eal/common/include/rte_vdev.h | 2 + lib/librte_eal/linuxapp/eal/rte_eal_version.map | 3 + 9 files changed, 401 insertions(+), 38 deletions(-) -- 2.1.4