From patchwork Tue Jan 30 00:59:16 2024 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alan Brady X-Patchwork-Id: 13536620 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) (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 E920722086 for ; Tue, 30 Jan 2024 00:59:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.9 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706576372; cv=none; b=bOVKnXxJA26+8rchiyqgA1WRDWpOdNxF12xNppbxoi87iw+BWYfyQRY7DplQUuk3TQVsz9yoSUaZGqpyTto6EOPJnqT2WkehEcgQVHyhvgvdEMhOolTpmlj93+d/K7PhZB3UtVNhZUO2j/DlM3mAX40ntcn/8yEwyEY2rTZzjW0= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706576372; c=relaxed/simple; bh=31U3/evWvSue/1pXyfyll8P9RkMZd2wlhYJ4cdwBbP4=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=r4hB4D9nJd+J2xw470nOMny4HPfS4+eoiNMqAR/4crpvkFXxGM2yGyVCkjok3wvj6WjDTDsTkyoxRv3qp5GolIvm5r8DO3/yBNmG6dK2C07A3O+FWJznXnYWKgGwSMf0Dt2D+GkmdJcizNz8KaQJHrC+HrBfq3Kn6vTrDOooB94= 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=GCLHoJ0G; arc=none smtp.client-ip=192.198.163.9 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="GCLHoJ0G" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1706576371; x=1738112371; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=31U3/evWvSue/1pXyfyll8P9RkMZd2wlhYJ4cdwBbP4=; b=GCLHoJ0GhIPTSsPneEiRxN5rnyGE6njM1UrUSoe+OOK7rbdKx7DBsLr3 hPd0+MMB/js4E2IyRq3kUWa4DQ0ufcKhpZ5vHDBlviqCP4pAdNqfR5GgX 7wCDLrNVCzfljZ1BFTF5R7OD0hsqkIVpLzItBrWx9JhBrVyc/bkKCdPlS d4TvYIcOuBDsLAwCD7kpJ31KQaKsvQHWd3unuB2hf+O+Sv+o8gtpP+gcs 3qZZhFrsSVnGbpXdnzB6Ai66R5jiAHpQtF4oAUoeCOBoUKQJ1Nvp2Ts2n PcXrsJSoNTlj65wJA1PDYd2flYAGOmczPzJX6QX/NrpZTPVgSIhoxxyiJ w==; X-IronPort-AV: E=McAfee;i="6600,9927,10968"; a="9870828" X-IronPort-AV: E=Sophos;i="6.05,227,1701158400"; d="scan'208";a="9870828" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2024 16:59:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10968"; a="1119078054" X-IronPort-AV: E=Sophos;i="6.05,227,1701158400"; d="scan'208";a="1119078054" Received: from dev1-atbrady.jf.intel.com ([10.166.241.35]) by fmsmga005.fm.intel.com with ESMTP; 29 Jan 2024 16:59:29 -0800 From: Alan Brady To: intel-wired-lan@lists.osuosl.org Cc: netdev@vger.kernel.org, przemyslaw.kitszel@intel.com, igor.bagnucki@intel.com, willemdebruijn.kernel@gmail.com, Alan Brady Subject: [PATCH v3 0/7 iwl-next] idpf: refactor virtchnl messages Date: Mon, 29 Jan 2024 16:59:16 -0800 Message-Id: <20240130005923.983026-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. Alan Brady (7): 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 drivers/net/ethernet/intel/idpf/idpf.h | 192 +- .../ethernet/intel/idpf/idpf_controlq_api.h | 5 + drivers/net/ethernet/intel/idpf/idpf_lib.c | 29 +- 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 | 2191 ++++++++--------- 6 files changed, 1086 insertions(+), 1336 deletions(-)