From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 4963442D2E; Fri, 23 Jun 2023 10:53:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C622640EE4; Fri, 23 Jun 2023 10:53:38 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 738D340E09 for ; Fri, 23 Jun 2023 10:53:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1687510416; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZXljv7GY/iG3EQDavIw077+ltgpNfBcAnZgEa62/Dvc=; b=ezZhKLaO2iSgpoAuw8t5GGsLTK8XzL44xzZdgkMRHwvyrjQgnSnJMHU4OmrNoMwjs0uGEi i1+XrWwMTPNE5s07WfYKgetI/y5pXIfCRpKT6+CEaksoa2eqISmkjvnWdchupcGwvDbTLT cIV21h1GrNIQQnZ3mqNpQ2sgvDOqSD0= Received: from mail-pg1-f199.google.com (mail-pg1-f199.google.com [209.85.215.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-213-KmfJbTUoNl6ksGa-JkTHnA-1; Fri, 23 Jun 2023 04:53:35 -0400 X-MC-Unique: KmfJbTUoNl6ksGa-JkTHnA-1 Received: by mail-pg1-f199.google.com with SMTP id 41be03b00d2f7-5575f8a7e1aso277263a12.3 for ; Fri, 23 Jun 2023 01:53:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687510414; x=1690102414; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ZXljv7GY/iG3EQDavIw077+ltgpNfBcAnZgEa62/Dvc=; b=Fd/RQzKAgiqmZsd1yPUKtV9FC65Zds6GEfHXx0ZUOCOvrv7/ZHUqSOvMNctmIYk42e maAKIrAwAMcUzJWhrq/+M95EPs5SivHiivIdfRS2Wi2t5i3rNii4cE37Im+/an6ASa8Q vsXifK8g56ZQod7an52qckJ7YEOy4sqLx5NHR/nAFw+xbyIRYHWqKAvrtsX06afPeEfI AEr8t/QR6/swoksD6sI2J1LItwf+RFcOGkR+Ut7zOnrWZT3YP8KA1wk7o/i4IMi+zzmj p+Zf5A6+d8wPwDykezFcKLtQLaRh4hIEFHWgfwh3QgT1cJzjV8iua3zY5Eet9XuT9zxy ZTpg== X-Gm-Message-State: AC+VfDygdxpvFitl/r/iv3J65mfh0p0X3qsiukHsyXTeY4/rBcCqguzc nHKLCeJcLpmvrn9VSPl93uBVGlCtxfPqoOxgvlPt6ixJ5V0vZYidYoHtDCXttbjiGLrYVpapKAv iknVgkRe1+h/aKQfq+Oo= X-Received: by 2002:a05:6a20:3ca7:b0:121:bc20:f6c8 with SMTP id b39-20020a056a203ca700b00121bc20f6c8mr13038328pzj.18.1687510414285; Fri, 23 Jun 2023 01:53:34 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4WSgf+joF3A/1ceWWftCSJmpRQ+c8d9ZVj+nt8F+aGrJ5Umv1la0oSSxK3J64InbxoEtztxwpzQUB/tbFZ+no= X-Received: by 2002:a05:6a20:3ca7:b0:121:bc20:f6c8 with SMTP id b39-20020a056a203ca700b00121bc20f6c8mr13038319pzj.18.1687510413980; Fri, 23 Jun 2023 01:53:33 -0700 (PDT) MIME-Version: 1.0 References: <1679084388-19267-1-git-send-email-roretzla@linux.microsoft.com> <1686087947-15471-1-git-send-email-roretzla@linux.microsoft.com> <20230609151320.GA1770@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> In-Reply-To: From: David Marchand Date: Fri, 23 Jun 2023 10:53:22 +0200 Message-ID: Subject: Re: [PATCH v5 0/6] replace rte atomics with GCC builtin atomics To: Patrick Robb Cc: Tyler Retzlaff , dev@dpdk.org, Qiming Yang , Qi Zhang , Wenjun Wu , thomas@monjalon.net X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello Patrick, On Thu, Jun 22, 2023 at 10:00=E2=80=AFPM Patrick Robb w= rote: > > I want to report a possible regression from this patch series seen from C= I testing on our Intel 82599ES 10G NIC, which we failed to report to patchw= ork when this initially went under CI due to a bug in our Jenkins reporting= scripts. Use of the ixgbe driver appears to be affected. Tyler I apologize= for the issues seen with reporting. We've made some temporary changes to a= void this happening again, and are currently reworking our reporting proces= s entirely to provide greater reliability. > > Here is a DTS snippet showing the issue, and the full log for the failing= virtio_smoke test can be downloaded here: https://dpdkdashboard.iol.unh.ed= u/results/dashboard/patchsets/26560/ > > 06/06/2023 18:22:58 TestVirtioSmoke: Start send packets an= d verify > 06/06/2023 18:22:58 tester: ifconfig enp134s0f0 m= tu 9000 > 06/06/2023 18:22:58 tester: > 06/06/2023 18:42:59 TestVirtioSmoke: Test Case test_virtio= _pvp Result FAILED: TIMEOUT on port start 0 > 06/06/2023 18:42:59 TestVirtioSmoke: port start 0 > > ixgbe_dev_wait_setup_link_complete(): IXGBE link thread not complete too = long time! > ixgbe_dev_wait_setup_link_complete(): IXGBE link thread not complete too = long time! > ixgbe_dev_wait_setup_link_complete(): IXGBE link thread not complete too = long time! > > We initially took this Intel10G testing offline to investigate as we thou= ght it was a lab infra failure. Obviously that wasn't the case, so ideally = we will bring this back online when appropriate. But, I don't want to do so= right now and start failing everyone's patchseries which are obviously unr= elated to this. Comments on this are welcome, otherwise of course I will ju= st return this test coverage to our CI when the state of the git tree allow= s for it. > > Apologies for the missing report and the timeline on this. We are taking = action to deliver results more reliably going forward. (reduced the cc list a bit) This is probably the same issue than what was reported by Intel validation: https://bugs.dpdk.org/show_bug.cgi?id=3D1249 A fix has been merged in next-net-intel, it will reach the main repo soon. https://git.dpdk.org/next/dpdk-next-net-intel/commit/?id=3Dfe4ce0aee766969a= 0e27fe28ced8ee7c761a2c4e --=20 David Marchand