Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp869202ybj; Tue, 5 May 2020 08:49:31 -0700 (PDT) X-Google-Smtp-Source: APiQypKTgVrzFYT+CB6KwNBeIKZr6SqHAuGSDUHbDFpmXmB/msJzzJeZrrB+mU1/kTrgQqpwjnUg X-Received: by 2002:a17:907:7242:: with SMTP id ds2mr3335868ejc.297.1588693771086; Tue, 05 May 2020 08:49:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588693771; cv=none; d=google.com; s=arc-20160816; b=peZ5Dpt9GxyJxWY2GiIyO8HvIkEFzJ/557JNg3dwb8UfWSj6o7D0hjg6SfkSiJjou9 JdLLRoib/prqQzWQabm1quAz3VXamUVOmOMuPCu5quO4DbcJnuylwAOJEYCft3EvMAWH q+tTaItp3N7/v9uEB99wQzQVbGzzJ9gce93EkFBEUp3OR3PuABxrdQJNtaW+iBt/h0Cu Sy9zzfGa3hlYCxLdzeeXT8C539mYgOhcN3ATfBX5+nEXhrdOqYyvZu02q2AaJvcF3ml7 QsoXa8zdDCrJkwCFchND4e3V9Kmv1LjWncHZXThG/7/XH0A2zH9t+zZwYjbUFsM8X8T1 FIEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:in-reply-to:message-id:date :subject:cc:to:from:ironport-sdr:dkim-signature; bh=qgL+UrIHPggA/cbMIcuZ6L6wlHkLvvYMOzgo5iwxhgg=; b=MKIU9O0bzOrg7EnfwsFb4esRBSCWX7KlfVyFgcqIMyuRzhjnLDpf7sEk+4YLoE5XB9 mUDcMiojdPRxLSw9lD467TvCHqx48y90hpC8aqEa4PkLVSAnGZGMZM8gBBLz7ovPjTeG XDn7G1sob37oP3hOT01/pm8++tlLkoM+mk5TzACeob9pguNkdI7hfTq5HX+r7LP9tGjD CCYckAgrmQiz3Ra0URsGQdLDWXXGn/+Tddwv9zR6QwJLsFgufMOJ5hSVre499JBLgQrF 35vDp9gpYXVKV+tqup+u0dV3qu4QDel6bB9al36eeMJd0WXhr6AMX+nHzfp0yL+sAsKU 6u4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amazon.com header.s=amazon201209 header.b=G+Q7z7KL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amazon.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z13si1408381eju.18.2020.05.05.08.49.08; Tue, 05 May 2020 08:49:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@amazon.com header.s=amazon201209 header.b=G+Q7z7KL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=amazon.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730430AbgEEPr2 (ORCPT + 99 others); Tue, 5 May 2020 11:47:28 -0400 Received: from smtp-fw-9101.amazon.com ([207.171.184.25]:63427 "EHLO smtp-fw-9101.amazon.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729406AbgEEPr1 (ORCPT ); Tue, 5 May 2020 11:47:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1588693647; x=1620229647; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=qgL+UrIHPggA/cbMIcuZ6L6wlHkLvvYMOzgo5iwxhgg=; b=G+Q7z7KLHWVXnfTXL6vCm+I433aihc4qv6kJ4WtoMTKroRNfPk1h2ODX OF6z/eK/BT306TyXHZLwicMXlh1LxUV8H66LNNDTsbf9ehFMfjnYhlQjE jI8MAGvELZ+s45fCv7TLThd3hP0hjX2NmaUVQsLs2nttVoml0/fnqvhKa U=; IronPort-SDR: O166hFl/kUUCS2stThOFXVSw6unJMOC3/77W9R3kUjp/BSPJ10ib3NA17O1H6Lb1AtOuv/GJ+Y 1lR6gvyLhizA== X-IronPort-AV: E=Sophos;i="5.73,355,1583193600"; d="scan'208";a="33074496" Received: from sea32-co-svc-lb4-vlan3.sea.corp.amazon.com (HELO email-inbound-relay-1d-5dd976cd.us-east-1.amazon.com) ([10.47.23.38]) by smtp-border-fw-out-9101.sea19.amazon.com with ESMTP; 05 May 2020 15:47:24 +0000 Received: from EX13MTAUEA002.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan3.iad.amazon.com [10.40.159.166]) by email-inbound-relay-1d-5dd976cd.us-east-1.amazon.com (Postfix) with ESMTPS id DA09DA225F; Tue, 5 May 2020 15:47:20 +0000 (UTC) Received: from EX13D31EUA001.ant.amazon.com (10.43.165.15) by EX13MTAUEA002.ant.amazon.com (10.43.61.77) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 May 2020 15:47:20 +0000 Received: from u886c93fd17d25d.ant.amazon.com (10.43.162.38) by EX13D31EUA001.ant.amazon.com (10.43.165.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 May 2020 15:47:12 +0000 From: SeongJae Park To: Eric Dumazet CC: SeongJae Park , Eric Dumazet , David Miller , Al Viro , "Jakub Kicinski" , Greg Kroah-Hartman , , netdev , LKML , SeongJae Park , , , Subject: Re: Re: [PATCH net v2 0/2] Revert the 'socket_alloc' life cycle change Date: Tue, 5 May 2020 17:46:44 +0200 Message-ID: <20200505154644.18997-1-sjpark@amazon.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: (raw) MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.43.162.38] X-ClientProxiedBy: EX13D18UWC003.ant.amazon.com (10.43.162.237) To EX13D31EUA001.ant.amazon.com (10.43.165.15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 5 May 2020 08:20:50 -0700 Eric Dumazet wrote: > > > On 5/5/20 8:07 AM, SeongJae Park wrote: > > On Tue, 5 May 2020 07:53:39 -0700 Eric Dumazet wrote: > > > > >> Why do we have 10,000,000 objects around ? Could this be because of > >> some RCU problem ? > > > > Mainly because of a long RCU grace period, as you guess. I have no idea how > > the grace period became so long in this case. > > > > As my test machine was a virtual machine instance, I guess RCU readers > > preemption[1] like problem might affected this. > > > > [1] https://www.usenix.org/system/files/conference/atc17/atc17-prasad.pdf > > > >> > >> Once Al patches reverted, do you have 10,000,000 sock_alloc around ? > > > > Yes, both the old kernel that prior to Al's patches and the recent kernel > > reverting the Al's patches didn't reproduce the problem. > > > > I repeat my question : Do you have 10,000,000 (smaller) objects kept in slab caches ? > > TCP sockets use the (very complex, error prone) SLAB_TYPESAFE_BY_RCU, but not the struct socket_wq > object that was allocated in sock_alloc_inode() before Al patches. > > These objects should be visible in kmalloc-64 kmem cache. Not exactly the 10,000,000, as it is only the possible highest number, but I was able to observe clear exponential increase of the number of the objects using slabtop. Before the start of the problematic workload, the number of objects of 'kmalloc-64' was 5760, but I was able to observe the number increase to 1,136,576. OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME before: 5760 5088 88% 0.06K 90 64 360K kmalloc-64 after: 1136576 1136576 100% 0.06K 17759 64 71036K kmalloc-64 Thanks, SeongJae Park