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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B4C4CC43334 for ; Wed, 20 Jul 2022 12:46:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230312AbiGTMqm (ORCPT ); Wed, 20 Jul 2022 08:46:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48278 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229511AbiGTMql (ORCPT ); Wed, 20 Jul 2022 08:46:41 -0400 Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F39FA1EC5B for ; Wed, 20 Jul 2022 05:46:40 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id t2-20020a17090a4e4200b001f21572f3a4so2093344pjl.0 for ; Wed, 20 Jul 2022 05:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=from:to:cc:in-reply-to:references:subject:message-id:date :mime-version:content-transfer-encoding; bh=a+qtmzzXRmiCZLPtii0K4DVzu9nTbF3p2kDITsU2fc4=; b=OFJC5vfD+HFETrKRo6YNhpbeXtd7/CtGhte1S9RcEq1IZyUCMFAtdnJ0vncTQyO9ib tdv9l2n8XJYzRHnu22TxJ0FsgLrMkd/QI70CkhbwbWPtM2TXklIw2Ou8yyt8WM9F7vw0 YdcnsklkM53aF2f4qBhqJ2gIfFVnHH5tCU/aXdbcOqfJkh22iz7GcxplMPv+sDd5i7gG MKv0xFG55i0/G/GOnQ/Mr5JD4zo1m5gKA3L9ZR3R0nC09Vl4OtQ095Ar2IqDxNKJ9DR3 6Qu2IizsQwNrhbr+7MqMlOwiSbSVFD1EBzpb9hT30pERgGd59oa2s2ONxZkWu5+EBSq1 K8Vg== 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:in-reply-to:references:subject :message-id:date:mime-version:content-transfer-encoding; bh=a+qtmzzXRmiCZLPtii0K4DVzu9nTbF3p2kDITsU2fc4=; b=qOYkcSpI+asE1W/XKDbvb6adb3tKfkKodGEJxRglu67sgcJsP5qWpsAQpUVWWiBMDH Af6GHEPkUvqRxod8lNdDQ9LoS0AIVX1/YQN3jLbEXZ52lC1kPAxvuvlLp0c2EbkmVdCV c8ggmkgVZF8cq3EJ8vuhQkigEy0ygG+fiaMOnOQ62zRzeMIJ9csw9I5e62yBF1E8ZuBy Hd6JSeHORh//J6sC7KLrKeMntPaxgMMWbpArtpvs7l6y4Fy2A2D60p4SFZhEm4Troggr lpo+0nklfKQ2xwgYpNvJsj/BlBazTqJLZpWPNTqq++86B5xJdXQ1glkw2gOB1GiFFNKT Basw== X-Gm-Message-State: AJIora/Xbbx48YPyGsuEhGKL3p+OB9norMsCtNi6d5IXQLUfH8qR3G9Q UsAgRtjhQNvKUtE6CdoW4iFHZg== X-Google-Smtp-Source: AGRyM1u6GT0s6u9syKNvfuPPJk2baUy+NE+VTFS47oj6wtMrKn3Cd9Y/VsJfGJceJsfSuj4cfizvqQ== X-Received: by 2002:a17:90b:1997:b0:1ef:7bcd:e8c3 with SMTP id mv23-20020a17090b199700b001ef7bcde8c3mr5340706pjb.55.1658321200411; Wed, 20 Jul 2022 05:46:40 -0700 (PDT) Received: from [127.0.1.1] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id o17-20020a170902d4d100b0016be9fa6807sm3173171plg.284.2022.07.20.05.46.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Jul 2022 05:46:39 -0700 (PDT) From: Jens Axboe To: netdev@vger.kernel.org, asml.silence@gmail.com, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org Cc: davem@davemloft.net, kuba@kernel.org, willemb@google.com, jonathan.lemon@gmail.com, kernel-team@fb.com, dsahern@kernel.org In-Reply-To: References: Subject: Re: (subset) [PATCH net-next v5 00/27] io_uring zerocopy send Message-Id: <165832119923.248138.16883055488620625980.b4-ty@kernel.dk> Date: Wed, 20 Jul 2022 06:46:39 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Tue, 12 Jul 2022 21:52:24 +0100, Pavel Begunkov wrote: > NOTE: Not to be picked directly. After getting necessary acks, I'll be > working out merging with Jakub and Jens. > > The patchset implements io_uring zerocopy send. It works with both registered > and normal buffers, mixing is allowed but not recommended. Apart from usual > request completions, just as with MSG_ZEROCOPY, io_uring separately notifies > the userspace when buffers are freed and can be reused (see API design below), > which is delivered into io_uring's Completion Queue. Those "buffer-free" > notifications are not necessarily per request, but the userspace has control > over it and should explicitly attaching a number of requests to a single > notification. The series also adds some internal optimisations when used with > registered buffers like removing page referencing. > > [...] Applied, thanks! [12/27] io_uring: initialise msghdr::msg_ubuf commit: 06f241e2bf4ba2a3e77269be25d21c0196a57a4f [13/27] io_uring: export io_put_task() commit: ba64c07a6ef9a05ca9eb09e13b70df7500e78cf8 [14/27] io_uring: add zc notification infrastructure commit: 6f322c753daee4b9d4ad494d4e8b05da610d804c [15/27] io_uring: cache struct io_notif commit: cf49e2d47c49e547d4bc370efe73785fc82354e5 [16/27] io_uring: complete notifiers in tw commit: 9cc16ae447db07d210175d2ad2419784dd20f784 [17/27] io_uring: add rsrc referencing for notifiers commit: e133e289093ea35c1f7f940fe4c0ceb62037dc59 [18/27] io_uring: add notification slot registration commit: f20b817fd29b64ef6de24b83ef23e1f3fb273967 [19/27] io_uring: wire send zc request type commit: 480ec5ff9a5a75d68423c0bd02e57a9ee6325320 [20/27] io_uring: account locked pages for non-fixed zc commit: fcb98e61d0232cff7dd14ae85ad1c88d68f98273 [21/27] io_uring: allow to pass addr into sendzc commit: 7ab12997edc9aa3e2be4169f929c50a1fcd41004 [22/27] io_uring: sendzc with fixed buffers commit: bb4019de9ea11d21137b4a8ff01d9e338071d633 [23/27] io_uring: flush notifiers after sendzc commit: 95a70c191696da64a6ae235d52132a5c17866dae [24/27] io_uring: rename IORING_OP_FILES_UPDATE commit: d488e605a45192f9f60c7624d46ba0b8c4d93aab [25/27] io_uring: add zc notification flush requests commit: cb155defb9bf20a647c8825a085695f3f94fdb60 [26/27] io_uring: enable managed frags with register buffers commit: 04ae3dbe8a027cf10ab759456ffc4fb119486f74 [27/27] selftests/io_uring: test zerocopy send commit: 0c450de20ce7d6bc8a2f97c98387baf910454477 Best regards, -- Jens Axboe