Received: by 2002:a05:6358:111d:b0:dc:6189:e246 with SMTP id f29csp1192575rwi; Thu, 3 Nov 2022 02:12:58 -0700 (PDT) X-Google-Smtp-Source: AMsMyM55/eXL7nWi0kgDf0/N7v1SLKtZh21kxe44rrkVAlL6sWUe6jbWMVJG0cEunh6qV0n7NE8p X-Received: by 2002:a17:90b:806:b0:213:473e:6fab with SMTP id bk6-20020a17090b080600b00213473e6fabmr29274870pjb.245.1667466778473; Thu, 03 Nov 2022 02:12:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667466778; cv=none; d=google.com; s=arc-20160816; b=qJIKqYdm7ZDZ1KAH46yhWn760F4icTp2GYjYu2uXa3JuI/ZifENq2f+Q++x98GNH46 UnL2SHx7s6GeLsbvor6uLHqT8CTYDeRZ18BVmr9e+mdYH9d/dYC4cl/FPbg8gXVi0zj2 PxIevFHm/+39pOhHcISfIaZjglQNHZ0+RVDJ4n210ZyadumgjHUdqxdqANzKqyKGhpcB KRHiqdENIz/Z/IMtLTRRqtI5bhfZbIsp5GyecVDuVBHzXyPMidGMbittOkpZIy+KkiMo kBfTZm9E9qg0UK0BusYlDwbOJHkqSFsvsqum4ks4YvuP/2pqQEITwLrtJO+I2qIpXCi7 mIVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=FeqABZBo26005zjL1Br5RZrJuJL5HVgW06cRmiuIaZg=; b=xHbNFgR2Nw8z4hmHyHqrvTLol4iG+cSSnDNPG1oZ8tIucwrBdGviyVHX8Cl86zz34n sCV5AxvDtIkGGFCfdL9E4pb7UEW3eCYkuoMIcJDoCB9XlkqyFtuXJrp07mY7RM6I4EVd FziHSs7hKskchXQVaExL1+hte0vQH7ieChKvCCBRrCDvUd7bnry9U0LsFCumFbmu9qUx xtdfgFKPD99L6sk3udIoWk2fCyA0OlIlmT7ioY8JWIC4bMuk2+fXg6i4HbMFc9H2cOKu O3YFXscBSDcJo3hvDSRaLf9H+tOw3wylvERaRIokiFHH/kTls0Tp6SunHH0rFN8WGvWl 3jvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hAe7c+oo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v12-20020a63f84c000000b0041c8dfb29f0si356325pgj.705.2022.11.03.02.12.46; Thu, 03 Nov 2022 02:12:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hAe7c+oo; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231297AbiKCIva (ORCPT + 97 others); Thu, 3 Nov 2022 04:51:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52282 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229379AbiKCIv1 (ORCPT ); Thu, 3 Nov 2022 04:51:27 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A11BD2DA for ; Thu, 3 Nov 2022 01:50:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1667465428; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=FeqABZBo26005zjL1Br5RZrJuJL5HVgW06cRmiuIaZg=; b=hAe7c+oox8n9rrYyuKYT6zujshRu2HaAQlSmtwZSGzQUsGDMMiUDuhhZXZgkh5FJlRKXfN xBuN9F9SYqA4e316fF5t0WvEu69/Ps2MEmcLd79BNKDGZKNohuhinahiGn52894B2iIB/o LOmqwCSyClFn4LYzpSZGld/qxkagcas= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-100-LeVvhBuJPlGnBUxBUZBlrw-1; Thu, 03 Nov 2022 04:50:25 -0400 X-MC-Unique: LeVvhBuJPlGnBUxBUZBlrw-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 165491C0513A; Thu, 3 Nov 2022 08:50:25 +0000 (UTC) Received: from localhost (ovpn-8-20.pek2.redhat.com [10.72.8.20]) by smtp.corp.redhat.com (Postfix) with ESMTP id B7B9839D6A; Thu, 3 Nov 2022 08:50:23 +0000 (UTC) From: Ming Lei To: Jens Axboe , io-uring@vger.kernel.org Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Miklos Szeredi , Stefan Hajnoczi , ZiyangZhang , Ming Lei Subject: [RFC PATCH 0/4] io_uring/splice: extend splice for supporting ublk zero copy Date: Thu, 3 Nov 2022 16:50:00 +0800 Message-Id: <20221103085004.1029763-1-ming.lei@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Guys, This patch extends io_uring/splice by adding two flags(SPLICE_F_DIRECT & SPLICE_F_READ_TO_READ) for supporting ublk zero copy, and fuse could benefit from the change too. - SPLICE_F_DIRECT is for using do_splice_direct() to support zero copy - SPLICE_F_READ_TO_READ is for supporting ublk READ zero copy, the plain splice can support WRITE zero copy by: splice(ublkc_fd, ublkc_pos, pipe_wr_fd, NULL, len, flags) splice(pipe_rd_fd, NULL, backing_fd, backing_off, len, flags) but can't support READ zc. Extend splice to allow to splice from the 1st ->splice_read()(producer) to the 2nd ->splice_read()(consumer), then READ request pages reference can be transferred to backing IO code path. The initial idea is suggested by Miklos Szeredi & Stefan Hajnoczi. The patchset has been verified basically by ublk builtin tests(loop/008, loop/009, generic/003), and basic mount, git clone, kernel building, umount tests on ublk-loop[1] which is created by 'ublk add -t loop -f $backing -z'. The next step is to allow io_uring to run do_splice_direct*() in async style like normal async RW instead of offloading to iowq context, so that top performance can be reached, and that depends on current work. Any comments are welcome. [1] https://github.com/ming1/ubdsrv/commits/splice-zc Ming Lei (4): io_uring/splice: support do_splice_direct fs/splice: add helper of splice_dismiss_pipe() io_uring/splice: support splice from ->splice_read to ->splice_read ublk_drv: support splice based read/write zero copy drivers/block/ublk_drv.c | 151 +++++++++++++++++++++++++- fs/read_write.c | 5 +- fs/splice.c | 193 +++++++++++++++++++++++++++++----- include/linux/fs.h | 2 + include/linux/pipe_fs_i.h | 9 ++ include/linux/splice.h | 14 +++ include/uapi/linux/ublk_cmd.h | 34 +++++- io_uring/splice.c | 16 ++- 8 files changed, 392 insertions(+), 32 deletions(-) -- 2.31.1