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 001C4C6FD19 for ; Thu, 16 Mar 2023 17:29:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229952AbjCPR3N (ORCPT ); Thu, 16 Mar 2023 13:29:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42420 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229892AbjCPR3E (ORCPT ); Thu, 16 Mar 2023 13:29:04 -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 5BE5AAB098 for ; Thu, 16 Mar 2023 10:28:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678987694; 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: in-reply-to:in-reply-to:references:references; bh=7hzxcSRtKQlA0e6rFrTWceT+M7ty2llKw335P2T8iHI=; b=HGpuGBGS2nae9I3ZjqN8i077lRmLPdA/ahemwokdwQOctpEmvObFc9fkfcOChK3PFj2UHA AvUqpeJuchXxE26uAYmn1l15ArYi6NSM3fid5K/EfJshjo/JR6Sx8+VdLivDgGtLiD5ks0 vuPLE4DuxXNOWmR6DWbpV9trSo5IHcc= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-128-X_O2pjKoObCWcsos-J3Lyg-1; Thu, 16 Mar 2023 13:28:11 -0400 X-MC-Unique: X_O2pjKoObCWcsos-J3Lyg-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 9BAE7857FBF; Thu, 16 Mar 2023 17:28:05 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5EDC135454; Thu, 16 Mar 2023 17:28:03 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <4EDC79DC-0C32-40FD-9C35-164C7A077922@oracle.com> References: <4EDC79DC-0C32-40FD-9C35-164C7A077922@oracle.com> <20230316152618.711970-1-dhowells@redhat.com> <20230316152618.711970-28-dhowells@redhat.com> <3DFBF27C-A62B-4AFE-87FD-3DF53FC39E8E@hammerspace.com> To: Chuck Lever III Cc: dhowells@redhat.com, Trond Myklebust , Matthew Wilcox , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Al Viro , Christoph Hellwig , Jens Axboe , Jeffrey Layton , Christian Brauner , Linus Torvalds , "netdev@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , Anna Schumaker , Linux NFS Mailing List Subject: Re: [RFC PATCH 27/28] sunrpc: Use sendmsg(MSG_SPLICE_PAGES) rather then sendpage MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <782775.1678987682.1@warthog.procyon.org.uk> Content-Transfer-Encoding: quoted-printable Date: Thu, 16 Mar 2023 17:28:02 +0000 Message-ID: <782776.1678987682@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Chuck Lever III wrote: > That means I haven't seen the cover letter and do not have any > context for this proposed change. https://lore.kernel.org/linux-fsdevel/20230316152618.711970-1-dhowells@red= hat.com/ > We've tried combining the sendpages calls in here before. It > results in a significant and measurable performance regression. > See: > = > da1661b93bf4 ("SUNRPC: Teach server to use xprt_sock_sendmsg for socket = sends") The commit replaced the use of sendpage with sendmsg, but that took away t= he zerocopy aspect of sendpage. The idea behind MSG_SPLICE_PAGES is that it allows you to do keep that. I'll have to try reapplying this commit and adding the MSG_SPLICE_PAGES flag. > Therefore, this kind of change needs to be accompanied by both > benchmark results and some field testing to convince me it won't > cause harm. Yep. > And, we have to make certain that this doesn't break operation > with kTLS sockets... do they support MSG_SPLICE_PAGES ? I haven't yet tackled AF_TLS, AF_KCM or AF_SMC as they seem significantly = more complex than TCP and UDP. I thought I'd get some feedback on what I have before I tried my hand at those. David