From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gaetan.rivet@6wind.com> Received: from mail-wr0-f180.google.com (mail-wr0-f180.google.com [209.85.128.180]) by dpdk.org (Postfix) with ESMTP id 23B762BBB for <dev@dpdk.org>; Thu, 15 Jun 2017 23:22:50 +0200 (CEST) Received: by mail-wr0-f180.google.com with SMTP id r103so28865658wrb.0 for <dev@dpdk.org>; Thu, 15 Jun 2017 14:22:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=V/K6qtRkwW6tgsneoT+g4+CG8uT0noFYGrnavI+Fzqw=; b=Ypr3gWFjZnFYgIJkLF+6DVxZB/o34t/Af+i6KeUA/Pk/TGZecMGe8i+L84etIgsRa2 STQzHiGsKnLtJMvNsrbSsGgyz0fwnntbJvI7Aok4hHTyiq8sPSjdIMROU7IT+gH8haCn ml/TDtDPGOmwuo3U4yEUREzyUbd06zMjq60FhlPisem1yEIE3oRydCFTWXVM9CKrIIiT wx3P35XTAjJU8x+43eMsW0/BVyY3zAdiph2ACNu+GsSkJ2Q4In9gFlOvgNss7sCm6nOg 31CNkXLBjA8qlJCc8cBPNBL2as80BdPQxquaOgZ6+1rrgyKpQxJxWkWrPh+i3Vg/qPJ1 2DpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=V/K6qtRkwW6tgsneoT+g4+CG8uT0noFYGrnavI+Fzqw=; b=BfZo9uYPzBzyUirvdz2bVMTTaxj0NGEDPQg4wHHdrb1eTLl5PziXs5Xrt1b4cSxh36 QWOLHi/nzbbIFSMNHQRBo/rZcuggERJ7uFc+gg0orAXjHAaS/pCPMHZn4o/a4duyPhez FGEpVrURzpo2JQ6+vCGw2zSWAbW8z9PfJ6jbbNwoDqOB/wyTnY6CKlLJiBAeuJ6RS2Y2 VP+a/ruSlujqcOwYYDJUgkqpWR690a0+ggnVlJne335JhfvHGO/3ZsaiXi31t1aWuWVx QxFBTod9vPfYFxTmW++Q1V4fFOTCB+t+ocFNqEbMA1D3TKLF0QjPxvC3idvWmi+T+Vxi L0zg== X-Gm-Message-State: AKS2vOwV5SjVp2O3CL2J+z8DUlrp+Qbjf3un2GUiR8FTe5vf5rnjfW2E oM1itJhK8us2bE13 X-Received: by 10.223.157.25 with SMTP id k25mr5426282wre.156.1497561769701; Thu, 15 Jun 2017 14:22:49 -0700 (PDT) Received: from bidouze.vm.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id v96sm304999wrc.53.2017.06.15.14.22.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jun 2017 14:22:48 -0700 (PDT) Date: Thu, 15 Jun 2017 23:22:40 +0200 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet <gaetan.rivet@6wind.com> To: "Wu, Jingjing" <jingjing.wu@intel.com> Cc: "Guo, Jia" <jia.guo@intel.com>, "Zhang, Helin" <helin.zhang@intel.com>, "Richardson, Bruce" <bruce.richardson@intel.com>, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, "Liu, Yuanhan" <yuanhan.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org> Message-ID: <20170615212240.GE29091@bidouze.vm.6wind.com> References: <1495986280-26207-1-git-send-email-jia.guo@intel.com> <20170530071400.GN14914@bidouze.vm.6wind.com> <9BB6961774997848B5B42BEC655768F810D9C9FA@SHSMSX103.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9BB6961774997848B5B42BEC655768F810D9C9FA@SHSMSX103.ccr.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [RFC] Add hot plug event in rte eal interrupt and inplement it in i40e driver. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 15 Jun 2017 21:22:50 -0000 Hi Jingjing, On Wed, Jun 07, 2017 at 07:40:37AM +0000, Wu, Jingjing wrote: > > > > > >Secondly, in order to read out the uevent that monitoring, we need to add uevent API in rte > > layer. We plan add 2 , rte_uevent_connect and rte_get_uevent. All driver interrupt handler > > could use these API to enable the uevent monitoring, and read out the uevent type , then > > corresponding to handle these uevent, such as detach the device when get the remove type. > > > > > > > I find having a generic uevent API interesting. > > > > However, all specifics pertaining to UIO use (hotplug_fd, subsystem > > enum) should stay in UIO specific code (eal_pci_uio.c?). > > > Yes, but it can be also considered as interrupt mechanism, right? > Sure. > > I am currently moving the PCI bus out of the EAL. EAL subsystems should > > not rely on PCI specifics, as they won't be available afterward. > > Will the interrupt handling be kept in EAL, right? > Ah yes, I was actually mistaken and thought more UIO parts would be moving. > > It should also allow you to clean up your API. Exposing hotplug_fd and > > requiring PMDs to link it can be avoided and should result in a simpler > > API. > Didn't get the idea. Why it will result in a simpler API? Is there any patch help > Me to understand? > How do you demux the hotplug_fd for several drivers / device? -- Gaëtan Rivet 6WIND