From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68]) by dpdk.org (Postfix) with ESMTP id B46E658D4 for ; Wed, 10 Aug 2016 13:00:41 +0200 (CEST) Received: by mail-wm0-f68.google.com with SMTP id i138so8767736wmf.3 for ; Wed, 10 Aug 2016 04:00:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=SolipIkjDEn9W7n0VzJmaF7nuSi3EdRVTstRnPO8Kd4=; b=lPugxEpj7fpVIFKmrrUlGap6s1OHZmO8Ng7xdPHGkClk/uuCmLNFAIm0b78TbNRXNL L5bthdl1nJdMdJ4/STm5VtbY4Yk5lYbnuwyG6tzCpEPQrzUcHw91J7ORxjxQGjwcuTcL cx45zEJ4m5PuSu2zQDcyd1/6bMiy9I08jIT8BTa/Sv2aKjDtVKy6B13KvTkC72JsNmRN RX+sprL0vhQY8E9gSlMoLUhsXtd+ZRF7x1s9R5JZaZs6Fhu+f2DQRzepsd/AtlQ/bGLZ Y2QPfzcKIeiUyPuib87alcuDvBKnR9hve/VTNeoXtSEZ1208nbm/g/gYLRPxSEkGj07R 2rTw== 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-transfer-encoding; bh=SolipIkjDEn9W7n0VzJmaF7nuSi3EdRVTstRnPO8Kd4=; b=Izo6eiJXgmIzm8TBm07WRW8gw/gY1MJXEN4tGe857BRQkKn+4QeWE9K4zr5A4IKGet eQ6/yhiSaRk+LqiTSnDsjjRAdoW1R1kTtE4Wm619Y+1aDQwu6tmJ452ZP2Wlt5Nvf4sj pBcCw+f+1Ql6ASDWKjQIeImxOe6lpkzweALPPpi4N1OmW3Xc+c3rFdADlG877CkDNrI2 /jOf4NmOamkqdJNmMn9VZYOrxODUK87Ljdfhn+8P82dFZkYN4sV74n5L8CGlnWoHwtQ8 QkdLTW7o1tKrCU9GYfExs0ZA6kmmV5OYRa5Qbesn3F7Soa4d9eGKZt+ULs5PtneU3pJN vhNQ== X-Gm-Message-State: AEkoousRXLEAdnihHN/ob91PC9J73Qqh7IfiUqascX2zKtJXhlD8Y0OpNSEuYrMyLCNtnr9AI2vmifgeLsQ9Uw== X-Received: by 10.28.109.197 with SMTP id b66mr2499146wmi.68.1470826841491; Wed, 10 Aug 2016 04:00:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.5.229 with HTTP; Wed, 10 Aug 2016 04:00:40 -0700 (PDT) In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E032F7520@shsmsx102.ccr.corp.intel.com> References: <2DBBFF226F7CF64BAFCA79B681719D9502044162@shsmsx102.ccr.corp.intel.com> <82F45D86ADE5454A95A89742C8D1410E032F7520@shsmsx102.ccr.corp.intel.com> From: =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= Date: Wed, 10 Aug 2016 13:00:40 +0200 Message-ID: To: "Xu, Qian Q" Cc: "Yao, Lei A" , "Topel, Bjorn" , "Wu, Jingjing" , "dev@dpdk.org" , Thomas Monjalon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] l3fwd can't launch on VF when we use i40e 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: Wed, 10 Aug 2016 11:00:42 -0000 Firstly, sorry about the late reply. > From my view, crc-strip is not a "MUST" check for the port start. We can = configure the value after > the port start. > Any thoughts? >>From my perspective, a non-supported configuration should return an error code to the API user. > Do you know is there any way I can bypass this when I use l3fwd? One work-around is enabling .hw_strip_crc for i40 VFs at runtime, by e.g. using rte_eth_dev_info_get() to determine what driver that's in use. That, however, does require a l3fwd patch. Bj=C3=B6rn