From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by dpdk.org (Postfix) with ESMTP id 434C53B5 for ; Tue, 2 May 2017 14:20:18 +0200 (CEST) Received: by mail-wm0-f52.google.com with SMTP id m123so17683681wma.0 for ; Tue, 02 May 2017 05:20:18 -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=tLUL3vzsoh3jVpswtXwkPj+a4X6XZVUV16rLefSiKk8=; b=YAx3bnNNY+r/JdlwWlhL6AuCe+xAn+/IwnR5uascFJRqOYheQuAOOqQ20+mBdcaWcJ tq+Gov4cQB1zZs4OigDtQTFOaizSzb609YnNQOrmZZ1Pva/PyAu0aPpzu5YgDNxR5WL8 vvJUJFVg7OSSPDzmv7TZSbCP2+bfTFV1uJhZEZEhbH1+uddcTG2YO0SezsR77xeqCuqd hQPP78dQolo0lkks9DtfTl9+kYL6hiILl95zJ1UA3OB42wAiESnLtZto3qTAe/JcEFbM LqFNJSvomaQuUV/ZS9qDq72Ced/OiM9zHrKc4uFAeOGYg7hye/s46JVVt9nXR8rTFcdc 6K2A== 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=tLUL3vzsoh3jVpswtXwkPj+a4X6XZVUV16rLefSiKk8=; b=UMgOtMf9DZ1yzQMMlq0xmpIQOJTlCrRzOe/a7ok7yqN55q7vsrlVNj5wQOZAGEke8V ONxIJmQcIaqYHwWue0tZf5/X7gYBbFdD8CaiLdhWANku1sRk19i7yxZ9/tHJszpygYkr suOuwjD8SjH7g6xh7RzteZsX/SY5oXIky/oJbn4QRi7dPFOfQesxiSYDdd5ja9DUaS9c f1/7hmK+TUpOrn/g/937rwKHZMetH76oKK14sZYqztdPGlJ2mpyD/pZQYNMAkvZwI7ud /HlgXR1wfCP/wvYOkykXxNgfpvoRfuKErrM5u9B5Yl2YmzJgJ98DZhJA11yfp49XlLcz 1bpg== X-Gm-Message-State: AN3rC/4dtBVtlxqLE8GbgEXR+M/y/ZKrZ4696ta1KC85zQroWjyM6xxb ti8AZxxmQ2HDaRll X-Received: by 10.28.109.220 with SMTP id b89mr2062634wmi.21.1493727618020; Tue, 02 May 2017 05:20:18 -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 4sm7586180wrv.33.2017.05.02.05.20.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 May 2017 05:20:17 -0700 (PDT) Date: Tue, 2 May 2017 14:20:10 +0200 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet To: Thomas Monjalon Cc: Jan Blunck , dev@dpdk.org, Billy McFall , Olivier MATZ , Ferruh Yigit , Elad Persiko Message-ID: <20170502122010.GF14914@bidouze.vm.6wind.com> References: <20170425090536.GS14914@bidouze.vm.6wind.com> <1493717377.6Zc0AIm2Fr@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1493717377.6Zc0AIm2Fr@xps> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v2 1/5] ethdev: introduce device removal event 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: Tue, 02 May 2017 12:20:18 -0000 On Tue, May 02, 2017 at 11:18:06AM +0200, Thomas Monjalon wrote: >02/05/2017 09:35, Jan Blunck: >> Am 25.04.2017 11:06 schrieb "Gaëtan Rivet" : >> >> Hi Ferruh, >> >> >> On Fri, Apr 21, 2017 at 03:59:24PM +0100, Ferruh Yigit wrote: >> >> > On 4/18/2017 1:17 PM, Gaetan Rivet wrote: >> > >> >> This new API allows reacting to a device removal. >> >> A device removal is the sudden disappearance of a device from its >> >> bus. >> >> >> > >> I don't think this belongs into ethdev. If it is bus related we need to >> expose this from it so that apps can register for the low level device >> being unplugged. > >Yes it sounds right. >We could work on device notifications. >We need to find a way of notifying the application that there is a >device event and that it affects one or more port at >ethdev/cryptodev/eventdev level. This is interesting. I developed this event with an easier integration in v17.05 in mind. It needs a proper generic implementation however (as suggested in [1]). I tried to have this discussion earlier[2], but without much interest. However, even with a bus-level event framework, we still need a way for drivers to advertize their support for specific events, and we still need to differentiate devices that are ready for specific events from those that do not. So I agree that it would be interesting to have a generic rte_device level interrupt framework to support generic events accross the whole board, but I'm not sure it would make the dichotomy between the *driver support* flag and the *device enabled* flag disappear. Regards, -- [1]: http://dpdk.org/ml/archives/dev/2017-April/064190.html [2]: http://dpdk.org/ml/archives/dev/2017-March/060998.html -- Gaëtan Rivet 6WIND