Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp26987405rwd; Mon, 3 Jul 2023 18:51:24 -0700 (PDT) X-Google-Smtp-Source: APBJJlHmQ9ocn2whbhuAYg/2Eq1/GlxhnDOhX8w/bIvjQ1zvWMJMs/v4FCQj9mq1XLqtSVOJZy2j X-Received: by 2002:a05:6a00:1a0b:b0:67e:4313:811e with SMTP id g11-20020a056a001a0b00b0067e4313811emr12466999pfv.0.1688435484482; Mon, 03 Jul 2023 18:51:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688435484; cv=none; d=google.com; s=arc-20160816; b=ZdiP3YMsOalN3E2ASrcef48zKb4hzbZL0OtbE5V6SwFk0UV+Lx+qYqQk1h7aQlLtO0 RSNqTOJXdsBD3DTEuhH1CNGvMrI6S6j6+2XJodHntXFA+tY8t8hE/5sGL4EQme0MT+yj Qk+4Hbta4Rk4B6ktaCxMAPa2xOJa4WqY9wCNCTBNn6o1lb74VHhxilcZS6SnVocYBsvt e67aIgRz4uJWr64c5uthj2ptVGA6PJmN7n21PR12wsKnJg8+ylrkUnTENgpI0PpQjK5d Hl5CGXsXbMdUKi8BMYNgzxTQmh9ZrZmyZg6KQRLmfG4chcczrK9XBVrNZ97gFvTck11G oe/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=DOJq0tNORprNso/owaCnpsoxEjiVBUfKRTWxWz3+eLs=; fh=0zUbo2ONdslUw7f7AO+5f/QBKtU64BoJsUr3zKH4I38=; b=Szu2Nj+JFdMUbVsOZTZak/pFjtc4m8I9t1IWnB41iaWVVACf8XYHVcyMEljHvAqjHw qSv1iJHRdQTEbEMXjTgvk9lUVV3Z1JUueFg4sV38PIszuWWJFfzcQkryXv/lZT0FRmaD N4nL287R1ocJDzp7piotR7bm2UeMWRv7TN6+uQ7+GJwdbp1INz/yt9cqOEnxzsc3KsFE hj2XDBU+6/bgKrYFyJ9al2Rk13LI3RBgsefw9l3TNnnRaVKMkBF0vUJHoesY1E32CEMF HACc9Lt7Kxkv3NKFIYnqo1K5qtPv8sqCktqU3vn8uyrFTfQnCntVQnH0iG1Ese0L53kx GKqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=s2sQtbg5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d9-20020a656209000000b005572b13d220si19748149pgv.343.2023.07.03.18.51.10; Mon, 03 Jul 2023 18:51:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-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=@kernel.org header.s=k20201202 header.b=s2sQtbg5; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230098AbjGDBrL (ORCPT + 99 others); Mon, 3 Jul 2023 21:47:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229505AbjGDBrK (ORCPT ); Mon, 3 Jul 2023 21:47:10 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E3E3FE4E for ; Mon, 3 Jul 2023 18:47:09 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D58C86108E for ; Tue, 4 Jul 2023 01:47:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B42AFC433C8; Tue, 4 Jul 2023 01:47:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1688435228; bh=dfMoSgYM5RJbBVtDZ4AdijqJoLEJkTdS1ggmGstPRi4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=s2sQtbg5DyXKSA75yI1JqRp/ek9ucPwULdZPI0EydB7q56o6u4Ok6kNO8ecPLY69J MmWW8kO9Q4L0aPHtKBDu1JIbuFC+Xb535rOBo75og023jwuUQPVm/ySFsMBfzLfJiL BhlPe+MDyp6WURItli1CZeOmS48OvvlDF3x/yoOkyiio8DkWnIDFHqiAvqiGpLEV6a ILE0rhN2V35xAchHNiSR2AwHWvS4cYaNWAoxM4PC+iXPxe+jaHRiq0NekN6/FaRqVM FpBmgwdcdFQYHxWeB0SZ0047iVjO0pzt/470wAGPdsM+AI5udML8l246JMMR/Zf9QE XkQ+t7jiKW3tg== Date: Mon, 3 Jul 2023 21:47:05 -0400 From: Chuck Lever To: NeilBrown Cc: linux-nfs@vger.kernel.org, Chuck Lever , lorenzo@kernel.org, jlayton@redhat.com, david@fromorbit.com Subject: Re: [PATCH v2 4/9] SUNRPC: Count ingress RPC messages per svc_pool Message-ID: References: <168842897573.139194.15893960758088950748.stgit@manet.1015granger.net> <168842927591.139194.16920372497489479670.stgit@manet.1015granger.net> <168843152047.8939.5788535164524204707@noble.neil.brown.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <168843152047.8939.5788535164524204707@noble.neil.brown.name> X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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-nfs@vger.kernel.org On Tue, Jul 04, 2023 at 10:45:20AM +1000, NeilBrown wrote: > On Tue, 04 Jul 2023, Chuck Lever wrote: > > From: Chuck Lever > > > > To get a sense of the average number of transport enqueue operations > > needed to process an incoming RPC message, re-use the "packets" pool > > stat. Track the number of complete RPC messages processed by each > > thread pool. > > If I understand this correctly, then I would say it differently. > > I think there are either zero or one transport enqueue operations for > each incoming RPC message. Is that correct? So the average would be in > (0,1]. > Wouldn't it be more natural to talk about the average number of incoming > RPC messages processed per enqueue operation? This would be typically > be around 1 on a lightly loaded server and would climb up as things get > busy. > > Was there a reason you wrote it the way around that you did? Yes: more than one enqueue is done per incoming RPC. For example, svc_data_ready() enqueues, and so does svc_xprt_receive(). If the RPC requires more than one call to ->recvfrom() to complete the receive operation, each one of those calls does an enqueue.