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 BA7F0C38145 for ; Sat, 3 Sep 2022 01:13:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230087AbiICBNN (ORCPT ); Fri, 2 Sep 2022 21:13:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53836 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229436AbiICBNM (ORCPT ); Fri, 2 Sep 2022 21:13:12 -0400 Received: from smtp-fw-80007.amazon.com (smtp-fw-80007.amazon.com [99.78.197.218]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 15391EEC79 for ; Fri, 2 Sep 2022 18:13:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1662167591; x=1693703591; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=VvyavOgooINWrhgMYO82Urjlf+KwAKz9XAW8osfdwg0=; b=P9gQKvwHMPWyxAfE5TX57uLum9osCgo73LrAApI+/PPbKTdkoykxgWhn 8YEKkSdS1wikQpS8MRYy02JSeGEoo7JlJAiRmLiTVgSwFj0yTwFv3SSHT UAWBoOdcbZtvbvFwgMvEmy5NfENdvgn5nIkQqivlxlR1xoY1um9hJRee5 Q=; X-IronPort-AV: E=Sophos;i="5.93,285,1654560000"; d="scan'208";a="126387247" Received: from pdx4-co-svc-p1-lb2-vlan3.amazon.com (HELO email-inbound-relay-iad-1a-c92fe759.us-east-1.amazon.com) ([10.25.36.214]) by smtp-border-fw-80007.pdx80.corp.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Sep 2022 01:12:55 +0000 Received: from EX13MTAUWB001.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan2.iad.amazon.com [10.40.163.34]) by email-inbound-relay-iad-1a-c92fe759.us-east-1.amazon.com (Postfix) with ESMTPS id 5D5FBC0272; Sat, 3 Sep 2022 01:12:54 +0000 (UTC) Received: from EX19D004ANA001.ant.amazon.com (10.37.240.138) by EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS) id 15.0.1497.38; Sat, 3 Sep 2022 01:12:53 +0000 Received: from 88665a182662.ant.amazon.com.com (10.43.160.120) by EX19D004ANA001.ant.amazon.com (10.37.240.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1118.12; Sat, 3 Sep 2022 01:12:51 +0000 From: Kuniyuki Iwashima To: CC: , , , , , Subject: Re: [PATCH v3 net-next 3/5] tcp: Access &tcp_hashinfo via net. Date: Fri, 2 Sep 2022 18:12:43 -0700 Message-ID: <20220903011243.93195-1-kuniyu@amazon.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.43.160.120] X-ClientProxiedBy: EX13D34UWC002.ant.amazon.com (10.43.162.137) To EX19D004ANA001.ant.amazon.com (10.37.240.138) Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org From: Eric Dumazet Date: Fri, 2 Sep 2022 17:53:18 -0700 > On Fri, Sep 2, 2022 at 5:44 PM Kuniyuki Iwashima wrote: > > > > From: Kuniyuki Iwashima > > Date: Thu, 1 Sep 2022 15:12:16 -0700 > > > From: Eric Dumazet > > > Date: Thu, 1 Sep 2022 14:30:43 -0700 > > > > On Thu, Sep 1, 2022 at 2:25 PM Kuniyuki Iwashima wrote: > > > > > > > > > > From: Paolo Abeni > > > > > > > > > > /Me is thinking aloud... > > > > > > > > > > > > I'm wondering if the above has some measurable negative effect for > > > > > > large deployments using only the main netns? > > > > > > > > > > > > Specifically, are net->ipv4.tcp_death_row and net->ipv4.tcp_death_row- > > > > > > >hashinfo already into the working set data for established socket? > > > > > > Would the above increase the WSS by 2 cache-lines? > > > > > > > > > > Currently, the death_row and hashinfo are touched around tw sockets or > > > > > connect(). If connections on the deployment are short-lived or frequently > > > > > initiated by itself, that would be host and included in WSS. > > > > > > > > > > If the workload is server and there's no active-close() socket or > > > > > connections are long-lived, then it might not be included in WSS. > > > > > But I think it's not likely than the former if the deployment is > > > > > large enough. > > > > > > > > > > If this change had large impact, then we could revert fbb8295248e1 > > > > > which converted net->ipv4.tcp_death_row into pointer for 0dad4087a86a > > > > > that tried to fire a TW timer after netns is freed, but 0dad4087a86a > > > > > has already reverted. > > > > > > > > > > > > Concern was fast path. > > > > > > > > Each incoming packet does a socket lookup. > > > > > > > > Fetching hashinfo (instead of &tcp_hashinfo) with a dereference of a > > > > field in 'struct net' might inccurr a new cache line miss. > > > > > > > > Previously, first cache line of tcp_info was enough to bring a lot of > > > > fields in cpu cache. > > > > > > Ok, let me test on that if there could be regressions. > > > > I tested tcp_hashinfo vs tcp_death_row->hashinfo with super_netperf > > and collected HW cache-related metrics with perf. > > > > After the patch the number of L1 miss seems to increase, but the > > instructions per cycle also increases, and cache miss rate did not > > change. Also, there was not performance regression for netperf. > > > > > > Tested: > > > > # cat perf_super_netperf > > echo 0 > /proc/sys/kernel/nmi_watchdog > > echo 3 > /proc/sys/vm/drop_caches > > > > perf stat -a \ > > -e cycles,instructions,cache-references,cache-misses,bus-cycles \ > > -e L1-dcache-loads,L1-dcache-load-misses,L1-dcache-stores \ > > -e dTLB-loads,dTLB-load-misses \ > > -e LLC-loads,LLC-load-misses,LLC-stores \ > > ./super_netperf $(($(nproc) * 2)) -H 10.0.0.142 -l 60 -fM > > > > echo 1 > /proc/sys/kernel/nmi_watchdog > > > > > > Before: > > > > # ./perf_super_netperf > > 2929.81 > > > > Performance counter stats for 'system wide': > > > > 494,002,600,338 cycles (23.07%) > > 241,230,662,890 instructions # 0.49 insn per cycle (30.76%) > > 6,303,603,008 cache-references (38.45%) > > 1,421,440,332 cache-misses # 22.550 % of all cache refs (46.15%) > > 4,861,179,308 bus-cycles (46.15%) > > 65,410,735,599 L1-dcache-loads (46.15%) > > 12,647,247,339 L1-dcache-load-misses # 19.34% of all L1-dcache accesses (30.77%) > > 32,912,656,369 L1-dcache-stores (30.77%) > > 66,015,779,361 dTLB-loads (30.77%) > > 81,293,994 dTLB-load-misses # 0.12% of all dTLB cache accesses (30.77%) > > 2,946,386,949 LLC-loads (30.77%) > > 257,223,942 LLC-load-misses # 8.73% of all LL-cache accesses (30.77%) > > 1,183,820,461 LLC-stores (15.38%) > > > > 62.132250590 seconds time elapsed > > > > This test will not be able to see a difference really... > > What is needed is to measure the latency when nothing at all is in the caches. > > Vast majority of real world TCP traffic is light or moderate. > Packets are received and cpu has to bring X cache lines into L1 in > order to process one packet. > > We slowly are increasing X over time :/ > > pahole is your friend, more than a stress-test. Here's pahole result on my local build. As Paolo said, we need 2 cachelines for tcp_death_row and the hashinfo? How about moving hashinfo as the first member of struct inet_timewait_death_row and convert it to just struct instead of pointer so that we need 1 cache line to read hashinfo? $ pahole -C netns_ipv4,inet_timewait_death_row vmlinux struct netns_ipv4 { struct inet_timewait_death_row * tcp_death_row; /* 0 8 */ struct ctl_table_header * forw_hdr; /* 8 8 */ struct ctl_table_header * frags_hdr; /* 16 8 */ struct ctl_table_header * ipv4_hdr; /* 24 8 */ struct ctl_table_header * route_hdr; /* 32 8 */ struct ctl_table_header * xfrm4_hdr; /* 40 8 */ struct ipv4_devconf * devconf_all; /* 48 8 */ struct ipv4_devconf * devconf_dflt; /* 56 8 */ /* --- cacheline 1 boundary (64 bytes) --- */ ... }; struct inet_timewait_death_row { refcount_t tw_refcount; /* 0 4 */ /* XXX 60 bytes hole, try to pack */ /* --- cacheline 1 boundary (64 bytes) --- */ struct inet_hashinfo * hashinfo __attribute__((__aligned__(64))); /* 64 8 */ int sysctl_max_tw_buckets; /* 72 4 */ /* size: 128, cachelines: 2, members: 3 */ /* sum members: 16, holes: 1, sum holes: 60 */ /* padding: 52 */ /* forced alignments: 1, forced holes: 1, sum forced holes: 60 */ } __attribute__((__aligned__(64)));