From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 483CAC48BC4 for ; Wed, 21 Feb 2024 00:50:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id C3534405C5; Wed, 21 Feb 2024 00:50:30 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mImM4R8Wn_aI; Wed, 21 Feb 2024 00:50:30 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=140.211.166.34; helo=ash.osuosl.org; envelope-from=intel-wired-lan-bounces@osuosl.org; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org E5465405F5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osuosl.org; s=default; t=1708476630; bh=GiXe1FeiM5N3pK8HZS1zhQoKwhRbDX6iCxbPRGCUhZs=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc:From; b=l/9z4gpZVXvj0JBIwBM+mefHcwkVZj2G7NkCoDCwbl1oI482GTR4axL/bnYoXugso skZW39kBhXpAFsiise0S5w9QCmGBzSRih5KTyBLtv/KYb26SuKEngbzjvM/+XGu//8 eCFGc38ROF3Ajg1zJI65ima8q3yKyvwgRFBxxzvqeczSrAKkYLN3apyAXkT/Ij+x4X kutAzzOHk1m+B0SOkSYRTz9SvAxvAOoAQFfNeUmPu0OCHoaeEBwxCpRgoVHhvw3Byq qskspQgO0VCVcPafHMCptU0NLBypH5kaCFf3EMwGJ5zcKQFHJswr07as28wqy5j5/s TwcbCikUEmv6A== Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp4.osuosl.org (Postfix) with ESMTP id E5465405F5; Wed, 21 Feb 2024 00:50:29 +0000 (UTC) Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by ash.osuosl.org (Postfix) with ESMTP id 9E1681BF39D for ; Wed, 21 Feb 2024 00:50:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 85D6F405F5 for ; Wed, 21 Feb 2024 00:50:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEZesiBMWbuz for ; Wed, 21 Feb 2024 00:50:27 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=192.198.163.18; helo=mgamail.intel.com; envelope-from=alan.brady@intel.com; receiver= DMARC-Filter: OpenDMARC Filter v1.4.2 smtp4.osuosl.org 4E2F6405C5 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 4E2F6405C5 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.18]) by smtp4.osuosl.org (Postfix) with ESMTPS id 4E2F6405C5 for ; Wed, 21 Feb 2024 00:50:26 +0000 (UTC) X-IronPort-AV: E=McAfee;i="6600,9927,10990"; a="2500693" X-IronPort-AV: E=Sophos;i="6.06,174,1705392000"; d="scan'208";a="2500693" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by fmvoesa112.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Feb 2024 16:50:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.06,174,1705392000"; d="scan'208";a="9550825" Received: from dev1-atbrady.jf.intel.com ([10.166.241.35]) by fmviesa004.fm.intel.com with ESMTP; 20 Feb 2024 16:50:25 -0800 From: Alan Brady To: intel-wired-lan@lists.osuosl.org Date: Tue, 20 Feb 2024 16:49:39 -0800 Message-ID: <20240221004949.2561972-1-alan.brady@intel.com> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Mailman-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1708476627; x=1740012627; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=b3K6fKvWYQ/SjUrArgoOKBdVwFRSn6xScwQTXGpC9rs=; b=F2+nNSOKNsookBOko9mf5zQ+FSOfCf9K57EOSUuEfV8glPDJYctb76bj yszmAHAa4PdB4yrHYrSaMelryjbn96ZL1S7R5ushpk9hRLnYNOm+PqTsG VVSjCYnSRra2lHGoVXZh4oWHpHPL7hUJ4fIBSUZx0BHbJ4jNeF7J2y6Ge QL6kcdd1hqXCmDJL2JOzD/ASeoeut3Ozo6v0+H9uoovJKJXdoFlpCRa2L M0ei6osd2mz+TfQGx6SCxovIRP3yUPTwOy9Oi4zoA4FlxINTYs+WL9hg5 wNDdtlILOf6SN5F0VCUXAisE5hEHJZ2nyUcA6dz7aZILNdIOsHDpM7e73 Q==; X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dmarc=pass (p=none dis=none) header.from=intel.com X-Mailman-Original-Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key, unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=F2+nNSOK Subject: [Intel-wired-lan] [PATCH v5 00/10 iwl-next] idpf: refactor virtchnl messages X-BeenThere: intel-wired-lan@osuosl.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Wired Ethernet Linux Kernel Driver Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: netdev@vger.kernel.org, Alan Brady Errors-To: intel-wired-lan-bounces@osuosl.org Sender: "Intel-wired-lan" 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. --- v1 -> v2: - don't take spin_lock in idpf_vc_xn_init, it's not needed - fix set but unused error on payload_size var in idpf_recv_mb_msg - prefer bitmap_fill and bitmap_zero if not setting an explicit range per documention - remove a couple unnecessary casts in idpf_send_get_stats_msg and idpf_send_get_rx_ptype_msg - split patch 4/6 such that the added functionality for MAC filters is separate v2 -> v3: - fix 'mac' -> 'MAC' in async handler error messages - fix size_t format specifier in async handler error message - change some variables to use auto-variables instead v3 -> v4: - revert changes to idpf_send_mb_msg that were introduced in v3, this will be addressed in future patch - tweak idpf_recv_mb_msg refactoring to avoid bailing out of the while loop when there are more messages to process and add comment in idpf_vc_xn_forward_reply about ENXIO - include some minor fixes to lower level ctrlq that seem like good candidates to add here - include fix to prevent deinit uninitialized vc core - remove idpf_send_dealloc_vectors_msg error v4 -> v5: - change signature on idpf_vc_xn_exec to accept a pointer @params argument instead of passing by value, also make it const --- 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(-) -- 2.43.0