From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 67A7CA3201 for ; Mon, 21 Oct 2019 10:55:10 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4279444C7; Mon, 21 Oct 2019 10:55:09 +0200 (CEST) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id 1D11334F0 for ; Mon, 21 Oct 2019 10:55:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1571648106; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5vVloWABpQw083QzVCvBjhchVKwGMGhm1i3Bw8pH3Us=; b=MwT1UNM0d8zCa9Mjd2kUB/LWq2KtocFyu506kzK2hCirjqnOZNAkfhJb606JN1D/Eeu8vj rGlxbylAPgsvlG2OG9Fkf2uzYqNXl1oBbbwWwOA8MYv2ipGwzriOj1HwLfSpyXXsd35+eT iCe5KIw/gdTOLqs1A+OAeeLvY7RxVjM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-382-qcsOQZRWMkmAv6pBgcVZqg-1; Mon, 21 Oct 2019 04:55:02 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 346FE1800DCA; Mon, 21 Oct 2019 08:55:00 +0000 (UTC) Received: from [10.36.118.52] (unknown [10.36.118.52]) by smtp.corp.redhat.com (Postfix) with ESMTP id 7FA4A5D9E2; Mon, 21 Oct 2019 08:54:55 +0000 (UTC) To: Ali Alnubani , Christian Ehrhardt , Abhishek Marathe , Ju-Hyoung Lee , "stable@dpdk.org" , "dev@dpdk.org" , Akhil Goyal , "benjamin.walker@intel.com" , David Christensen , Hemant Agrawal , Ian Stokes , Jerin Jacob , John McNamara , Luca Boccassi , Pei Zhang , "pingx.yu@intel.com" , "qian.q.xu@intel.com" , Raslan Darawsheh , Thomas Monjalon , "yuan.peng@intel.com" , "zhaoyan.chen@intel.com" References: <20190913163100.30002-1-ktraynor@redhat.com> <20191003132036.29258-1-ktraynor@redhat.com> <4cb0a062-0c12-caa0-16bf-6a9b78bef325@redhat.com> From: Kevin Traynor Message-ID: <51ffeea2-6395-f973-752d-be6d3713e41c@redhat.com> Date: Mon, 21 Oct 2019 09:54:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-MC-Unique: qcsOQZRWMkmAv6pBgcVZqg-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [dpdk-stable] 18.11.3 (LTS) patches review and test 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 20/10/2019 14:16, Ali Alnubani wrote: > Hi, >=20 > Replaying here because I can't find the first email in the thread. >=20 > Regarding testing results with Mellanox devices, we did basic functional = testing with testpmd, and don't see any issues. >=20 > Testing matrix: > - NIC: ConnectX-5 / OS: RHEL 7.4 / Kernel: 5.3.0 / Driver: rdma-core v25.= 1 / fw: 16.26.1040 > - NIC: ConnectX-4 Lx / OS: RHEL 7.4 / Kernel: 5.3.0 / Driver: rdma-core v= 25.1 / fw: 14.26.1040 > - NIC: ConnectX-5 / OS: RHEL 7.4 / Kernel: 3.10.0-693.el7.x86_64 / Driver= : MLNX_OFED_LINUX-4.7-1.0.0.1 / fw: 16.26.1040 > - NIC: ConnectX-4 Lx / OS: RHEL 7.4 / Kernel: 3.10.0-693.el7.x86_64 / Dri= ver: MLNX_OFED_LINUX-4.7-1.0.0.1 / fw: 14.26.1040 >=20 > I apologize for the delay in reporting our results. >=20 No problems, thanks for the testing Ali, Kevin. > Thanks, > Ali >=20 >> -----Original Message----- >> From: Christian Ehrhardt >> Sent: Thursday, October 17, 2019 4:55 PM >> To: Abhishek Marathe >> Cc: Kevin Traynor ; Ju-Hyoung Lee >> ; stable@dpdk.org; dev@dpdk.org; Akhil Goyal >> ; Ali Alnubani ; >> benjamin.walker@intel.com; David Christensen ; >> Hemant Agrawal ; Ian Stokes >> ; Jerin Jacob ; John McNamara >> ; Luca Boccassi ; Pei Zhang >> ; pingx.yu@intel.com; qian.q.xu@intel.com; Raslan >> Darawsheh ; Thomas Monjalon >> ; yuan.peng@intel.com; zhaoyan.chen@intel.com >> Subject: Re: [dpdk-dev] [dpdk-stable] 18.11.3 (LTS) patches review and t= est >> >> Azure image: 'Canonical UbuntuServer 18.04-DAILY-LTS latest': >>> >>> * PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED >>> * VERIFY-DPDK-OVS: PASSED >>> * VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED >>> * VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED >>> * PERF-DPDK-MULTICORE-PPS-F32: FAILED >> >> Hi Abhishek, >> since you use the daily LTS image and see such a significant change comp= ared >> to before, could it by any chance be that this made you switch from kern= el >> 4.15 to 5.0. >> Because by the normal HWE policy [1] this got into Bionic rebuilds and i= t >> seems [2] the same is true for linux-azure kernel flavours. >> >> Could you check your logs if the kernel version changed between the old = and >> the new runs? >> An alternative might be to rerun 18.11.2 to see if it drops as well, whi= ch might >> indicate that it wasn't 18.11.2 -> 18.11.3 but something else like the k= ernel. >> >> Not sure if that old kernel is ok, but you always can go back to what a = version >> was released with. So in this case package linux-azure=3D4.15.0.1009.9 i= s still >> there and you could try >> 18.11.3 with that maybe? >> >> Let me know if you need help changing kernels there. >> >> [1]: > >> [2]: > >=20