From patchwork Tue Apr 26 23:06:47 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Leonardo Bras X-Patchwork-Id: 12828053 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 lists.gnu.org (lists.gnu.org [209.51.188.17]) (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 BCD98C433F5 for ; Tue, 26 Apr 2022 23:08:54 +0000 (UTC) Received: from localhost ([::1]:36856 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1njUIf-0003hV-Kj for qemu-devel@archiver.kernel.org; Tue, 26 Apr 2022 19:08:53 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45136) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1njUHI-00015d-KG for qemu-devel@nongnu.org; Tue, 26 Apr 2022 19:07:28 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:48211) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1njUHF-00008D-Us for qemu-devel@nongnu.org; Tue, 26 Apr 2022 19:07:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1651014444; 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; bh=mQjdALwdJP/TMWP1xYmiBA6opd53OgC0gGNS3wDWJVI=; b=a6iStG65eC+mp5CzQmv5LvilbJkMmEKnKcph686ldSn3XcG2NA4NMIlsom0s68aVQGa0QL 8oudTqpCzQht5EnauMoq+TyrFpve/YollXS0H7Eif636tsMNu8Xxu7yyEBn2/9+n6ngqLf DDZP/fIsSzdGMF+TYHSE7Oq/fzFXEO0= Received: from mail-oo1-f70.google.com (mail-oo1-f70.google.com [209.85.161.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-266-UVwfjswSPuyywwwwe30rgQ-1; Tue, 26 Apr 2022 19:07:23 -0400 X-MC-Unique: UVwfjswSPuyywwwwe30rgQ-1 Received: by mail-oo1-f70.google.com with SMTP id k13-20020a4ad10d000000b003531756b915so185178oor.4 for ; Tue, 26 Apr 2022 16:07:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=mQjdALwdJP/TMWP1xYmiBA6opd53OgC0gGNS3wDWJVI=; b=l/Q0wQFcTWClMI8uL98jDHnjB2lOIo3TGp8sR95IBW6H+0RxPtDg43FcamEOqHyup3 ttfCXWaTpJVTEpahkU+t+Ae9NOSy9iYacscsALTa1a6/FC5ISWvATVt2tSkRmtn75geq avE44QYnwWs+84mFPYke59CHdPrLD92Kq7G7VCR4NWPZexwz+7yUYrmaccqIQlT3G4ZQ YTq2WzO8sPxBlOXekyJyb/I6NcMulAgfbhLdgg2Jp8Q/GmZmCbt2MmRtMpwgeuzsHOcZ g8yb/rGbiERNAKk1EPUOnrDLc2542ZSa7OECOOsy8+Ah66NNPsnCKk24DKBqdPBSkOsW a6dA== X-Gm-Message-State: AOAM5303sp+HP4kzh63MX12kmtDR7YQLHUDlU7ZZ9XAGGiAs5hyhtSgF a93pN72tw18y6TVFVjQ/18dRIT0LcYoFlDi4FfITN8LH0uOvf+H1X3yNEy/eUDh5Rk0ei6olxw1 BLlM62urhyriiKCg= X-Received: by 2002:a9d:6c93:0:b0:605:d7a8:7930 with SMTP id c19-20020a9d6c93000000b00605d7a87930mr1181113otr.254.1651014442506; Tue, 26 Apr 2022 16:07:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyqT+hjUurDGA5hi8GuYHFLAsnTDZqFPD79LrQU7SihUgoAwTfEsxHiV1EhYmKV8WGaxh4cOg== X-Received: by 2002:a9d:6c93:0:b0:605:d7a8:7930 with SMTP id c19-20020a9d6c93000000b00605d7a87930mr1181086otr.254.1651014442146; Tue, 26 Apr 2022 16:07:22 -0700 (PDT) Received: from LeoBras.redhat.com ([2804:431:c7f0:2ba0:92e8:26c9:ce7e:f03e]) by smtp.gmail.com with ESMTPSA id q4-20020a4a3004000000b0035e974ec923sm419855oof.2.2022.04.26.16.07.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Apr 2022 16:07:21 -0700 (PDT) From: Leonardo Bras To: =?utf-8?q?Marc-Andr=C3=A9_Lureau?= , Paolo Bonzini , Elena Ufimtseva , Jagannathan Raman , John G Johnson , =?utf-8?q?Daniel_P=2E_Berrang?= =?utf-8?q?=C3=A9?= , Juan Quintela , "Dr. David Alan Gilbert" , Eric Blake , Markus Armbruster , Fam Zheng , Peter Xu Subject: [PATCH v10 0/7] MSG_ZEROCOPY + multifd Date: Tue, 26 Apr 2022 20:06:47 -0300 Message-Id: <20220426230654.637939-1-leobras@redhat.com> X-Mailer: git-send-email 2.36.0 MIME-Version: 1.0 Received-SPF: pass client-ip=170.10.133.124; envelope-from=leobras@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -28 X-Spam_score: -2.9 X-Spam_bar: -- X-Spam_report: (-2.9 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.082, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Leonardo Bras , qemu-devel@nongnu.org, qemu-block@nongnu.org Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" This patch series intends to enable MSG_ZEROCOPY in QIOChannel, and make use of it for multifd migration performance improvement, by reducing cpu usage. Patch #1 creates new callbacks for QIOChannel, allowing the implementation of zero copy writing. Patch #2 implements io_writev flags and io_flush() on QIOChannelSocket, making use of MSG_ZEROCOPY on Linux. Patch #3 adds a "zero_copy_send" migration property, only available with CONFIG_LINUX, and compiled-out in any other architectures. This migration property has to be enabled before multifd migration starts. Patch #4 adds a helper function that allows to see if TLS is going to be used. This helper will be later used in patch #5. Patch #5 changes multifd_send_sync_main() so it returns int instead of void. The return value is used to understand if any error happened in the function, allowing migration to possible fail earlier. Patch #6 implements an workaround: The behavior introduced in d48c3a0445 is hard to deal with in zerocopy, so a workaround is introduced to send the header in a different syscall, without MSG_ZEROCOPY. Patch #7 Makes use of QIOChannelSocket zero_copy implementation on nocomp multifd migration. Results: In preliminary tests, the resource usage of __sys_sendmsg() reduced 15 times, and the overall migration took 13-22% less time, based in synthetic cpu workload. In further tests, it was noted that, on multifd migration with 8 channels: - On idle hosts, migration time reduced in 10% to 21%. - On hosts busy with heavy cpu stress (1 stress thread per cpu, but not cpu-pinned) migration time reduced in ~25% by enabling zero-copy. - On hosts with heavy cpu-pinned workloads (1 stress thread per cpu, cpu-pinned), migration time reducted in ~66% by enabling zero-copy. Above tests setup: - Sending and Receiving hosts: - CPU : Intel(R) Xeon(R) Platinum 8276L CPU @ 2.20GHz (448 CPUS) - Network card: E810-C (100Gbps) - >1TB RAM - QEMU: Upstream master branch + This patchset - Linux: Upstream v5.15 - VM configuration: - 28 VCPUs - 512GB RAM --- Changes since v9: - Patch #6 got simplified and improved (thanks Daniel) - Patch #7 got better comments (thanks Peter Xu) Changes since v8: - Inserted two new patches #5 & #6, previous patch #5 is now #7. - Workaround an optimization introduced in d48c3a0445 - Removed unnecessary assert in qio_channel_writev_full_all Changes since v7: - Migration property renamed from zero-copy to zero-copy-send - A few early tests added to help misconfigurations to fail earlier - qio_channel_full*_flags() renamed back to qio_channel_full*() - multifd_send_sync_main() reverted back to not receiving a flag, so it always sync zero-copy when enabled. - Improve code quality on a few points Changes since v6: - Remove io_writev_zero_copy(), and makes use of io_writev() new flags to achieve the same results. - Rename io_flush_zero_copy() to io_flush() - Previous patch #2 became too small, so it was squashed in previous patch #3 (now patch #2) Changes since v5: - flush_zero_copy now returns -1 on fail, 0 on success, and 1 when all processed writes were not able to use zerocopy in kernel. - qio_channel_socket_poll() removed, using qio_channel_wait() instead - ENOBUFS is now processed inside qio_channel_socket_writev_flags() - Most zerocopy parameter validation moved to migrate_params_check(), leaving only feature test to socket_outgoing_migration() callback - Naming went from *zerocopy to *zero_copy or *zero-copy, due to QAPI/QMP preferences - Improved docs Changes since v4: - 3 patches got splitted in 6 - Flush is used for syncing after each iteration, instead of only at the end - If zerocopy is not available, fail in connect instead of failing on write - 'multifd-zerocopy' property renamed to 'zerocopy' - Fail migrations that don't support zerocopy, if it's enabled. - Instead of checking for zerocopy at each write, save the flags in MultiFDSendParams->write_flags and use them on write - Reorganized flag usage in QIOChannelSocket - A lot of typos fixed - More doc on buffer restrictions Changes since v3: - QIOChannel interface names changed from io_async_{writev,flush} to io_{writev,flush}_zerocopy - Instead of falling back in case zerocopy is not implemented, return error and abort operation. - Flush now waits as long as needed, or return error in case anything goes wrong, aborting the operation. - Zerocopy is now conditional in multifd, being set by parameter multifd-zerocopy - Moves zerocopy_flush to multifd_send_sync_main() from multifd_save_cleanup so migration can abort if flush goes wrong. - Several other small improvements Changes since v2: - Patch #1: One more fallback - Patch #2: Fall back to sync if fails to lock buffer memory in MSG_ZEROCOPY send. Changes since v1: - Reimplemented the patchset using async_write + async_flush approach. - Implemented a flush to be able to tell whenever all data was written. Leonardo Bras (7): QIOChannel: Add flags on io_writev and introduce io_flush callback QIOChannelSocket: Implement io_writev zero copy flag & io_flush for CONFIG_LINUX migration: Add zero-copy-send parameter for QMP/HMP for Linux migration: Add migrate_use_tls() helper multifd: multifd_send_sync_main now returns negative on error multifd: Send header packet without flags if zero-copy-send is enabled multifd: Implement zero copy write in multifd migration (multifd-zero-copy) qapi/migration.json | 24 ++++++ include/io/channel-socket.h | 2 + include/io/channel.h | 38 +++++++++- migration/migration.h | 6 ++ migration/multifd.h | 4 +- chardev/char-io.c | 2 +- hw/remote/mpqemu-link.c | 2 +- io/channel-buffer.c | 1 + io/channel-command.c | 1 + io/channel-file.c | 1 + io/channel-socket.c | 110 +++++++++++++++++++++++++++- io/channel-tls.c | 1 + io/channel-websock.c | 1 + io/channel.c | 49 ++++++++++--- migration/channel.c | 3 +- migration/migration.c | 52 ++++++++++++- migration/multifd.c | 75 +++++++++++++++---- migration/ram.c | 29 ++++++-- migration/rdma.c | 1 + migration/socket.c | 12 ++- monitor/hmp-cmds.c | 6 ++ scsi/pr-manager-helper.c | 2 +- tests/unit/test-io-channel-socket.c | 1 + 23 files changed, 379 insertions(+), 44 deletions(-)