From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f176.google.com (mail-ob0-f176.google.com [209.85.214.176]) by dpdk.org (Postfix) with ESMTP id 3FB635677 for ; Mon, 15 Feb 2016 14:16:36 +0100 (CET) Received: by mail-ob0-f176.google.com with SMTP id wb13so211794937obb.1 for ; Mon, 15 Feb 2016 05:16:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OxNnpJMERJTv0K4KVlA+8J0dS8Nsccsi2H1PE7CuA0A=; b=FxjdN91rHxWAbX7tks7yVVOBbqCktAGcRHOEnK+nb10inHG00a1PO6BaMzmzz6oyWc AjsDsXZZRAFaJ5j0J7yABTtEYVypNoZlAHqCHhq9e7b5y4uN+kPGwuJXLemWaSC2+n9n BBbgufEPzAbRdNcmJNndF/brYr/lo/LbkRm5svkoYjl/RpPNaLoWcdx6WfZitYxMNd1e tE5KjnrZz7zk7SxxGaTPYpNrhK7lsa98kvEW9rnySKD4/e07Kza1g8Z2QzCLc5LjwbpH CddsOfPesGrhyeJVsIVIkLb5DLkBJ/xng2FeqVrfaC0cJX+ozmg12mah4gz9ijRESwqH nqoQ== 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:from:date :message-id:subject:to:cc:content-type; bh=OxNnpJMERJTv0K4KVlA+8J0dS8Nsccsi2H1PE7CuA0A=; b=IKH4IyXgz28+/uqjXPWKy76WWSGv/xsxgw5MXf2NGl1/5tEzVSp1kREpXcRweWKw2O +pjYv0ZE3iT33RsRdK6en9VEpusqLyKliy/25Gl5Pr6DuviYGoB08Gdq6sH6IAJqGfwu vXDW2Fx+AoCbGwvaJThiAgXBjnhxzqzc3Auwua9XaZWBKD6owWw2dMFJzwb/QJarDLA5 UoW4I5r3bjoRknsWXniaf2VsZ3PFTMBXNnSLDh9ynpaUtuR+cXxJqGtaiCkpsS65Fa/7 ootmW9OROqiBIHFLDAD0014XQ0zBM2ajCUQgye1kZ8JYSXPyqBs29Yz6AUI5VHsZmaVB 1JDw== X-Gm-Message-State: AG10YOT90SiLLMTxZI9lseLSa3tBY0/hfTFt+Penvda2lL8DJhBOephiHvnfE8TYZih8j9WiEEg/KbC5sPGNRePY X-Received: by 10.60.59.37 with SMTP id w5mr12045047oeq.44.1455542195737; Mon, 15 Feb 2016 05:16:35 -0800 (PST) MIME-Version: 1.0 Received: by 10.76.180.72 with HTTP; Mon, 15 Feb 2016 05:16:16 -0800 (PST) In-Reply-To: <9BB6961774997848B5B42BEC655768F8D98B60@SHSMSX104.ccr.corp.intel.com> References: <1452688307-20213-1-git-send-email-jingjing.wu@intel.com> <1453859378-23912-1-git-send-email-jingjing.wu@intel.com> <1453859378-23912-3-git-send-email-jingjing.wu@intel.com> <9BB6961774997848B5B42BEC655768F8D98B60@SHSMSX104.ccr.corp.intel.com> From: David Marchand Date: Mon, 15 Feb 2016 14:16:16 +0100 Message-ID: To: "Wu, Jingjing" Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 2/2] i40evf: support interrupt based pf reset request X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Feb 2016 13:16:36 -0000 Hello, On Sun, Feb 14, 2016 at 4:25 AM, Wu, Jingjing wrote: >> -----Original Message----- >> From: David Marchand [mailto:david.marchand@6wind.com] >> Having this infrastructure is one thing, but the initial problem was that the >> driver did not recover from this reset event. >> The linux i40e vf driver handles this kind of event itself. >> Could we have something similar ? >> > > Considering about the how to use DPDK PMD, and how to setup resource, we can > know that lots of resources are managed by application. I think based on current > PMD driver framework, driver cannot reset without application's help. I reported an issue on ixgbe. What you provide here is a workaround for i40e. I am not even sure this can be applied to ixgbe. Does it mean that anytime we have a problem with drivers, workarounds should be applied to ethdev / eal ... so that you don't have to handle anything in the drivers ? This is not the first time I complain about this kind of design issues. > If we need to support driver recovery automatically, we'd better to find a way to do that. > Do you have any idea? First, list those "lots of resources" that "are managed by application". If your driver needs to keep track of those, this is i40e driver job to do this internally without requiring ethdev to be modified. If this proves to be generic enough, maybe moving part of this to ethdev will then make sense. Thanks. -- David Marchand