From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 609B737A4 for ; Mon, 18 Apr 2016 20:47:22 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP; 18 Apr 2016 11:47:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,503,1455004800"; d="scan'208";a="787387040" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by orsmga003.jf.intel.com with ESMTP; 18 Apr 2016 11:47:19 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.12]) by IRSMSX101.ger.corp.intel.com ([169.254.1.157]) with mapi id 14.03.0248.002; Mon, 18 Apr 2016 19:47:18 +0100 From: "Topel, Bjorn" To: "Zhang, Helin" , David Marchand CC: "dev@dpdk.org" , "Wu, Jingjing" Thread-Topic: [dpdk-dev] [PATCH] i40evf: Ignore disabled HW CRC strip for Linux PF hosts Thread-Index: AQHRll4t4CE1BTYTBEOjYOMUsAEtBZ+KlriAgAAHiACABXbK5g== Date: Mon, 18 Apr 2016 18:47:18 +0000 Message-ID: <6B5F13689D63284BBB0B66A5B315C82DBAAD8C@IRSMSX103.ger.corp.intel.com> References: <1460645904-19565-1-git-send-email-bjorn.topel@intel.com> , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.3.86.135] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [PATCH] i40evf: Ignore disabled HW CRC strip for Linux PF hosts 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, 18 Apr 2016 18:47:22 -0000 >> Not sure this is the right way to handle it. The driver should >> return an error rather than silently discard what the >> application asked. > > I also think it should return an error with checking if the > host is kernel driver, and crc strip is disabled in VF. Thank > you David! Thanks for reviewing my patch, Helin and David. I agree that it's subtle to ignore the error, and just log the error. This is how ixgbevf behaves (refer to ixgbevf_dev_configure), so I figured that i40evf should behave analogous. I'll submit a v2 of the patch that returns an EINVAL and logs the failure. Would it make sense to change the ixgbevf_dev_configure as well, in a separate patch? >> ---------------------------------------------------------------------- >> Intel Sweden AB >> Registered Office: Isafjordsgatan 30B, 164 40 Kista, Stockholm, Sweden >> Registration Number: 556189-6027 >> >> This e-mail and any attachments may contain confidential material for >> the sole use of the intended recipient(s). Any review or distribution >> by others is strictly prohibited. If you are not the intended >> recipient, please contact the sender and delete all copies. > > Please, remove this. Noted. Will make sure to fix that for future revisions. Thanks! Bj=F6rn ---------------------------------------------------------------------- Intel Sweden AB Registered Office: Isafjordsgatan 30B, 164 40 Kista, Stockholm, Sweden Registration Number: 556189-6027 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.