From patchwork Tue Feb 6 03:37:54 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alan Brady X-Patchwork-Id: 13546603 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8830B2CA4 for ; Tue, 6 Feb 2024 03:38:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.16 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707190695; cv=none; b=EC0cGiYVGr/B7qoauaC25AzrMmMUQeGf9vKcmprcNzF6ptk1gZdQYTnO3bjj+PMYPsCPUI2KF0oSzeMsFmqXjROB+3gSZfrOlxyOCeH/fFO/rWeizgR/xp4oZsPDmOLrzaAq+MHXwQsxLEDL0j0mnqcBp01RAAh5FwYX9KsXe+Y= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707190695; c=relaxed/simple; bh=SivssqEd2AifeIrqAszgd/JFRTzLlRswVDVW8rQyOZw=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=Z5Ct+H15uh6GcnVaNy6PZzd/CAvf729sPmvE6ZZrOhzObw0Auskcgac2xBTjkgzA+ih2pTRvggfbx1yT0eCk1RSoXmYIHZJXm8i6Q8+A1Kpllhcg7TwBnv5Iv2BPuoBwP3blX9q/q5xyGdUpm730QfQAi5d4h4L2dzYAMEuXoyU= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=NdA5A+9b; arc=none smtp.client-ip=198.175.65.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="NdA5A+9b" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1707190694; x=1738726694; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=SivssqEd2AifeIrqAszgd/JFRTzLlRswVDVW8rQyOZw=; b=NdA5A+9b/V9pe2aGTEs4UifF/7W4YaBBBbjcboljlr5I11TUdEVTEUQY Q0LYwWS+le8/KPt4TnRYdUrEzsolz9zfchChPByVC/LU3KthunupWV8lB rJA5i4uVIK1OUIyyT/4sg9osS4KkZpsvDMSd/+KZq0SZS28X/Ddrk9PJ/ 6qAOoYlXLoi741bytlJgvfyWlx6fqUOYc/t5aTvKD/i5//qoVB3MnJoy1 fnEV6q+3YnB5oHLNeaqTBHH0vb/woTj4z6A6AAWdKubSPBO/vAJbexT5v Jm3iiAE/RiiDIW/yzcOE38ExRf5lUEDmA/1zy/xA/wZZinh5KMbjExNqN Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10975"; a="824746" X-IronPort-AV: E=Sophos;i="6.05,246,1701158400"; d="scan'208";a="824746" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by orvoesa108.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Feb 2024 19:38:14 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.05,246,1701158400"; d="scan'208";a="5653855" Received: from dev1-atbrady.jf.intel.com ([10.166.241.35]) by orviesa004.jf.intel.com with ESMTP; 05 Feb 2024 19:38:13 -0800 From: Alan Brady To: intel-wired-lan@lists.osuosl.org Cc: netdev@vger.kernel.org, willemdebruijn.kernel@gmail.com, przemyslaw.kitszel@intel.com, igor.bagnucki@intel.com, aleksander.lobakin@intel.com, Alan Brady Subject: [PATCH v4 00/10 iwl-next] idpf: refactor virtchnl messages Date: Mon, 5 Feb 2024 19:37:54 -0800 Message-Id: <20240206033804.1198416-1-alan.brady@intel.com> X-Mailer: git-send-email 2.40.1 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 The motivation for this series has two primary goals. We want to enable support of multiple simultaneous messages and make the channel more robust. The way it works right now, the driver can only send and receive a single message at a time and if something goes really wrong, it can lead to data corruption and strange bugs. This works by conceptualizing a send and receive as a "virtchnl transaction" (idpf_vc_xn) and introducing a "transaction manager" (idpf_vc_xn_manager). The vcxn_mngr will init a ring of transactions from which the driver will pop from a bitmap of free transactions to track in-flight messages. Instead of needing to handle a complicated send/recv for every a message, the driver now just needs to fill out a xn_params struct and hand it over to idpf_vc_xn_exec which will take care of all the messy bits. Once a message is sent and receives a reply, we leverage the completion API to signal the received buffer is ready to be used (assuming success, or an error code otherwise). At a low-level, this implements the "sw cookie" field of the virtchnl message descriptor to enable this. We have 16 bits we can put whatever we want and the recipient is required to apply the same cookie to the reply for that message. We use the first 8 bits as an index into the array of transactions to enable fast lookups and we use the second 8 bits as a salt to make sure each cookie is unique for that message. As transactions are received in arbitrary order, it's possible to reuse a transaction index and the salt guards against index conflicts to make certain the lookup is correct. As a primitive example, say index 1 is used with salt 1. The message times out without receiving a reply so index 1 is renewed to be ready for a new transaction, we report the timeout, and send the message again. Since index 1 is free to be used again now, index 1 is again sent but now salt is 2. This time we do get a reply, however it could be that the reply is _actually_ for the previous send index 1 with salt 1. Without the salt we would have no way of knowing for sure if it's the correct reply, but with we will know for certain. Through this conversion we also get several other benefits. We can now more appropriately handle asynchronously sent messages by providing space for a callback to be defined. This notably allows us to handle MAC filter failures better; previously we could potentially have stale, failed filters in our list, which shouldn't really have a major impact but is obviously not correct. I also managed to remove fairly significant more lines than I added which is a win in my book. Additionally, this converts some variables to use auto-variables where appropriate. This makes the alloc paths much cleaner and less prone to memory leaks. We also fix a few virtchnl related bugs while we're here. Alan Brady (10): idpf: implement virtchnl transaction manager idpf: refactor vport virtchnl messages idpf: refactor queue related virtchnl messages idpf: refactor remaining virtchnl messages idpf: add async_handler for MAC filter messages idpf: refactor idpf_recv_mb_msg idpf: cleanup virtchnl cruft idpf: prevent deinit uninitialized virtchnl core idpf: fix minor controlq issues idpf: remove dealloc vector msg err in idpf_intr_rel drivers/net/ethernet/intel/idpf/idpf.h | 194 +- .../net/ethernet/intel/idpf/idpf_controlq.c | 7 +- .../ethernet/intel/idpf/idpf_controlq_api.h | 5 + drivers/net/ethernet/intel/idpf/idpf_lib.c | 38 +- drivers/net/ethernet/intel/idpf/idpf_main.c | 3 +- drivers/net/ethernet/intel/idpf/idpf_vf_dev.c | 2 +- .../net/ethernet/intel/idpf/idpf_virtchnl.c | 2175 ++++++++--------- 7 files changed, 1096 insertions(+), 1328 deletions(-) Tested-by: Alexander Lobakin Tested-by: Alexander Lobakin