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 DD207424D8; Wed, 12 Jun 2024 06:38:25 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 03A4E40E5A; Wed, 12 Jun 2024 06:37:13 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.14]) by mails.dpdk.org (Postfix) with ESMTP id 3D8FE40E5A for ; Wed, 12 Jun 2024 06:37:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1718167032; x=1749703032; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=LN35K37FMpD5FvhLAlmiGEfNxwKXIhRTQEGypghfkCU=; b=S3tiPf3aZG4DaDmcaOkevmnTPI6loClmMwUjTWXKP5LfGbkFBoKp6nhu nEhyWHCkkubrpZPgErASK1GOV1SA4qMl+qS52+xsnUOht5rnIZK1T3K2M DwPlknO5wVJgTRmpPJnHWgNAzS3Nv64NgDrM4y1+r8gWnB5ijxKZOPCMj TXj/dgzOtPZ7zzFzTkQqyeeK3E0uPeokkWSNWTTwB6+92pN1noaBh196L wiInKjnjhn9pqJKebfnu4ZzF33wW4kkNMULcdqMMpUHjKBuyr2cELefyL d33qzM++/xHht7dzb4XTpUx/eBwXWYeAQ8dCzvEnWRtnRxpqF4Lh5SRww w==; X-CSE-ConnectionGUID: wOe9aUNpQISqAPddXA9okA== X-CSE-MsgGUID: 2su1KHmLSpqCXhNGLgJmPw== X-IronPort-AV: E=McAfee;i="6600,9927,11100"; a="18742211" X-IronPort-AV: E=Sophos;i="6.08,232,1712646000"; d="scan'208";a="18742211" Received: from orviesa008.jf.intel.com ([10.64.159.148]) by orvoesa106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jun 2024 21:37:11 -0700 X-CSE-ConnectionGUID: umIQqb8sQ6upMpKcrNKN2A== X-CSE-MsgGUID: AsXxCUJ2RGyfXHK3wAvtAw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.08,232,1712646000"; d="scan'208";a="40281980" Received: from unknown (HELO npf-hyd-clx-03..) ([10.145.170.182]) by orviesa008.jf.intel.com with ESMTP; 11 Jun 2024 21:37:09 -0700 From: Soumyadeep Hore To: bruce.richardson@intel.com, anatoly.burakov@intel.com Cc: dev@dpdk.org Subject: [PATCH v3 16/22] common/idpf: add wmb before tail Date: Wed, 12 Jun 2024 03:52:51 +0000 Message-ID: <20240612035257.2245824-17-soumyadeep.hore@intel.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240612035257.2245824-1-soumyadeep.hore@intel.com> References: <20240604080611.2197835-1-soumyadeep.hore@intel.com> <20240612035257.2245824-1-soumyadeep.hore@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 Introduced through customer's feedback in their attempt to address some bugs this introduces a memory barrier before posting ctlq tail. This makes sure memory writes have a chance to take place before HW starts messing with the descriptors. Signed-off-by: Soumyadeep Hore --- drivers/common/idpf/base/idpf_controlq.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/common/idpf/base/idpf_controlq.c b/drivers/common/idpf/base/idpf_controlq.c index bd23e54421..ba2e328122 100644 --- a/drivers/common/idpf/base/idpf_controlq.c +++ b/drivers/common/idpf/base/idpf_controlq.c @@ -624,6 +624,8 @@ int idpf_ctlq_post_rx_buffs(struct idpf_hw *hw, struct idpf_ctlq_info *cq, /* Wrap to end of end ring since current ntp is 0 */ cq->next_to_post = cq->ring_size - 1; + idpf_wmb(); + wr32(hw, cq->reg.tail, cq->next_to_post); } -- 2.43.0