From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 058C75911 for ; Tue, 25 Apr 2017 11:05:44 +0200 (CEST) Received: by mail-wm0-f46.google.com with SMTP id m123so89688807wma.0 for ; Tue, 25 Apr 2017 02:05:44 -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=1TomOz2X+F4mhguPUmdzKfoY2V023AhTKlbmHBtb/j8=; b=e0Ek1j3TSWfcem+LRK40zeqCdgaw2dxg5kUzIv3QDQBLbI9kkv0aI2zgEJI0CjE4yk ycbqEFQvPaqc0Vh6mU+pCGsLWgM8V9uXzdSXdbhCFAxs6fYlBkPTzJatBRq9lc9gu+Nn IJDOgrbDU49mAqcwpFTgloK7CuGhhppjGNW/NW8xyonqZN7MUZlmJ0Gb7YQ670K8CRT2 NKmZLMRDuEuLkaYU91b7pKMVDJbjmdTfUBtMh+0TNwiXv1+w2mkSBgeBwSQvqfy53oQ2 2ovgkuCOLuGJLCoYAnQOruX8L/eytjV76M5+mVxz1W3AHmi2TZTViGkYZcJMGU2du0Sw gUZw== 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=1TomOz2X+F4mhguPUmdzKfoY2V023AhTKlbmHBtb/j8=; b=hSEqXSFJoGN8x0KUmLUCa2mUG7B3B0+PsGGeMSAMRHWZJWd8BSDzbqTYA9QLI+359D 0p4TFGHRUZIDo2dquIBKTZ2tSWEoFy/ns1iH1lxGZ6bEBn9mOanuPvETFEHDJ6O3GSIE XhZA+IDT+TK486iDQG7eQTE+A5LJpBTPvxp3GrIO19QbBIs3vlZrTxWxHS/fcvF8v5vJ vmB+QZwNewXdwCbtIQHOdENKpA7a82mq2cxQx6N1BaUPLYl+0hQxYd335tGL8N5C8//K FcQ9UQQB+6Zys8mMUHrtuSLzKl6PFB0skGuTasVrB84yPE0hRe5YlNjv33FX9aCWKgNr JDdQ== X-Gm-Message-State: AN3rC/7EKEvRBeVqtVXKyfkGnUeYp/SDerYaIq2cfZwY3yGVNYdQtcVp PW6uysEvdsLyuA1y01k= X-Received: by 10.28.31.196 with SMTP id f187mr11892629wmf.117.1493111144622; Tue, 25 Apr 2017 02:05:44 -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 72sm1835386wmx.23.2017.04.25.02.05.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Apr 2017 02:05:43 -0700 (PDT) Date: Tue, 25 Apr 2017 11:05:36 +0200 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet To: Ferruh Yigit Cc: dev@dpdk.org, Elad Persiko , Thomas Monjalon , Olivier MATZ , Billy McFall Message-ID: <20170425090536.GS14914@bidouze.vm.6wind.com> References: <923e5a49-6514-4a28-fb89-81e196ae99c9@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <923e5a49-6514-4a28-fb89-81e196ae99c9@intel.com> 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, 25 Apr 2017 09:05:45 -0000 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. >> >> PMDs implementing support for this notification guarantee that the removal >> of the underlying device does not incur a risk to the application. >> >> In particular, Rx/Tx bursts and all other functions can still be called >> (albeit likely returning errors) without triggering a crash, irrespective >> of an application handling this event. >> >> Signed-off-by: Gaetan Rivet >> Signed-off-by: Elad Persiko > ><...> > >> diff --git a/doc/guides/nics/features/default.ini b/doc/guides/nics/features/default.ini >> index b1b9114..cafc6c7 100644 >> --- a/doc/guides/nics/features/default.ini >> +++ b/doc/guides/nics/features/default.ini >> @@ -10,6 +10,7 @@ >> Speed capabilities = >> Link status = >> Link status event = >> +Removal event = >> Queue status event = >> Rx interrupt = >> Free Tx mbuf on demand = > >This release a few NIC features added, and it is hard to follow them if >you are particularly looking for these features. > >So do you think does it make sense to put those new PMD features into >release notes to make it more visible? > Yes it seems like a good idea to announce this evolution. I will send the relevant patch for this soon. >Thanks, >ferruh -- Gaëtan Rivet 6WIND