From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) by dpdk.org (Postfix) with ESMTP id B7EF5C348 for ; Fri, 19 Feb 2016 17:22:00 +0100 (CET) Received: by mail-ig0-f169.google.com with SMTP id hb3so38328255igb.0 for ; Fri, 19 Feb 2016 08:22:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nofutznetworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=HFmmR3kEToVvdrnXf5AnlWPZzNenpdEg5xU2scn5aLQ=; b=uk4gA0nNs4EBvqbi+ASEwkjLU7CEbTd4V6yUHXi4ew7kvGPYK9VJzpaZXSC8FYT3Ak 0I1j4NMa1KFtCridF00ATv7Ui/ozHzobQPBuSE/EZn6rQNCdWtpmGpCTJPOS/coo7WBl Tyu9PkG9MIAO4aTq+kF1/Pt/MQTnw7ScnYWdqjhsgi1RHJTR7+BCiFcMUKeylF1wG7Xv wU+50smj2CdlwTT0iq1k3+PFpmu+DuWvwI5uPxPA4CCVUvXVkBmaq7cbkR3ytZGh2Ogf DiEcd88l2JWE6ox+zD1Zqcv3sDuvEd5QFnvzNguQ+uu3K4BpFhI3jEPeYRQVCnJxZx2j Pz4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=HFmmR3kEToVvdrnXf5AnlWPZzNenpdEg5xU2scn5aLQ=; b=LJsWc9FPEHyBFlmwtSj3qBQy4iUjDtXivLu7t1op2x1E3jDBmsp+DOgoj0vy8cQa55 rAhTLFIARbLiEgCDrVvATnwdcUYgJo7UBIN5CFbnsBqb8zpV9mMQ7c+EE+iTPuMLG197 tnH1iM+SE8znJIX3qzrtDG0WAxOYPPp2khUOx0BLe8SCcZmDN8PVO3XkPnhIRKjKs4/S tIG2yA4wM4s50GRm7B+AUKOQiggpnsVT3e4GG2jEHddpBAY3XnMRqN6qI86VZ8nOJw/X U44JslKVTqL0DPR0YzXhVBTdTC6S/7gOr3xbYrz+t/O7/M96vD0XN07wKOD5wrisZEwg oRTQ== X-Gm-Message-State: AG10YOQScmyZVllHqP39xwhXZgyGxoB9ZfSIleOfY+WWsf05QVrHU0AA8rcxvt+1TJ23DGp3PCyd87mHHdPZFg== MIME-Version: 1.0 X-Received: by 10.50.28.20 with SMTP id x20mr10172815igg.87.1455898920143; Fri, 19 Feb 2016 08:22:00 -0800 (PST) Received: by 10.107.3.75 with HTTP; Fri, 19 Feb 2016 08:22:00 -0800 (PST) In-Reply-To: <3AEA2BF9852C6F48A459DA490692831FFC5723@IRSMSX109.ger.corp.intel.com> References: <3AEA2BF9852C6F48A459DA490692831FFC5723@IRSMSX109.ger.corp.intel.com> Date: Fri, 19 Feb 2016 18:22:00 +0200 Message-ID: From: Lazaros Koromilas To: "Pattan, Reshma" Content-Type: text/plain; charset=UTF-8 Cc: "users@dpdk.org" Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary process X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 16:22:00 -0000 Thanks for your reply Reshma, that clears things up. Lazaros. On Fri, Feb 19, 2016 at 2:58 PM, Pattan, Reshma wrote: > Hi, > >> -----Original Message----- >> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Lazaros Koromilas >> Sent: Wednesday, February 17, 2016 11:40 AM >> To: users@dpdk.org >> Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary >> process >> >> On Wed, Feb 17, 2016 at 1:17 PM, Lazaros Koromilas >> wrote: >> > Hi all, >> > >> > I'm trying to take advantage of the multi-process support together >> > with the port hotplugging framework. The idea is that my primary >> > process will configure all ports I'm going to need and then secondary >> > processes will come up, selectively attach to ports and perform rx/tx. > > From quick glance of dpdk code what I see is rte_eth_dev_attach will not attach existing port to DPDK app. > Because from "librte_ether/rte_ethdev.c" rte_eth_dev_attach()==> rte_eth_dev_attach_vdev()==>rte_eal_vdev_init() creates new vdev and returns you the port id. > And moreover vdevs are local to process. > You may have to check clearly what is the hot plug functionality and do you really need it in your case. > >> > Where pcap{0,1}-in.pcap files are pcap dumps. The primary will >> > initialize the ports and pause(2). The secondary will attach to the >> > same ports and do work. The latter then segfaults in >> > rte_eth_rx_burst() with dev->data->{rx,tx}_queues being NULL pointers. >> > > > Since in secondary new device is created, but device configuration and queue configuration is not done, crash is expected. > > Thanks, > Reshma