Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4014028imm; Wed, 5 Sep 2018 09:19:47 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbvDv0qAVH7XOqvlsant2BvYnSBA2TCT8LsdxQYLB+Hgi2urfFt3sPDo3CFwck0J5/AZAww X-Received: by 2002:a65:560a:: with SMTP id l10-v6mr13475379pgs.130.1536164387127; Wed, 05 Sep 2018 09:19:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536164387; cv=none; d=google.com; s=arc-20160816; b=YALnLu7+h8RDibMh9RfU0YZEZxhy0z9Zymgk7JdU6SYgXkZ6OdqKXBgjip0aJBxM88 jpxQgX4KUOBLKxjRpiPpon0tjT98gbJCHfBYabz/xDlvOm/QxLxisc6cOPjS14scKdZl Ea1xZoJz/kzhy/ft9F6cfRCFtZpaHD8RlfFuzpvMN79lvMWyjJZVLmdvOU5HBfXfsCbN W3S59YAS856racHeg80wRZpcxvXEPX7cxi4QC+q3bPcr1Eg6c2C1Jpn+fXHJUTP/Va6L 35Xd9Hjqo/hsOuPjpstj+Vgu+ntkEQT34tTkzcEsBVnLadHJFhAedu+6uhTPpCQvKJO6 r9GQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject; bh=Gu8QNYwZFzgohW2iJBzsB1wr8wsZuCpl16aYMH4PZh8=; b=xV9PTgb80i+I3hZ57M03cOJU2Jr4w0agIE03aEFPFMoEOtWqVSOxyXUys8d2I24QlK ONff1tk95jAdbfaCN0eSKkBaWOdR1s2FRfbiSvhP+iNZhS6MQREJ4n8iIitq1jSEYxdd +Tu8dboeiVZ91v+yIeNDBcVBOczxz0m9HamCKVFQ7wTy8pqdIcBs5Ej5pV/02x6rZBiB D4SwtuKbOQj1TCbQW3Ud+2eEEtEDvoR1bRjOyTEipNskMzBJmCwkZ59d6guTZyjZPZXe i8+3hhixAZsjQbPKmIJmWwUK+V7BraNeRLi0N3QTxpXBWejQCxAH0P1awmAjT/ubPBjm CC4w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h185-v6si2348160pfc.172.2018.09.05.09.19.30; Wed, 05 Sep 2018 09:19:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727527AbeIEUtI (ORCPT + 99 others); Wed, 5 Sep 2018 16:49:08 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:38678 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726046AbeIEUtI (ORCPT ); Wed, 5 Sep 2018 16:49:08 -0400 Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w85GFhws071509 for ; Wed, 5 Sep 2018 12:18:13 -0400 Received: from e06smtp03.uk.ibm.com (e06smtp03.uk.ibm.com [195.75.94.99]) by mx0a-001b2d01.pphosted.com with ESMTP id 2maj3wshrs-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 05 Sep 2018 12:18:13 -0400 Received: from localhost by e06smtp03.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 5 Sep 2018 17:18:10 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp03.uk.ibm.com (192.168.101.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 5 Sep 2018 17:18:02 +0100 Received: from d06av24.portsmouth.uk.ibm.com (d06av24.portsmouth.uk.ibm.com [9.149.105.60]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w85GI1CT42991710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 5 Sep 2018 16:18:01 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 436414203F; Wed, 5 Sep 2018 19:17:56 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5F3ED42045; Wed, 5 Sep 2018 19:17:54 +0100 (BST) Received: from [9.145.21.228] (unknown [9.145.21.228]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 5 Sep 2018 19:17:54 +0100 (BST) Subject: Re: Plumbers 2018 - Performance and Scalability Microconference To: Christopher Lameter , Daniel Jordan Cc: linux-kernel@vger.kernel.org, "linux-mm@kvack.org" , Aaron Lu , alex.kogan@oracle.com, akpm@linux-foundation.org, boqun.feng@gmail.com, brouer@redhat.com, dave@stgolabs.net, dave.dice@oracle.com, Dhaval Giani , ktkhai@virtuozzo.com, Pavel.Tatashin@microsoft.com, paulmck@linux.vnet.ibm.com, shady.issa@oracle.com, tariqt@mellanox.com, tglx@linutronix.de, tim.c.chen@intel.com, vbabka@suse.cz, longman@redhat.com, yang.shi@linux.alibaba.com, shy828301@gmail.com, Huang Ying , subhra.mazumdar@oracle.com, Steven Sistare , jwadams@google.com, ashwinch@google.com, sqazi@google.com, Shakeel Butt , walken@google.com, rientjes@google.com, junaids@google.com, Neha Agarwal References: <1dc80ff6-f53f-ae89-be29-3408bf7d69cc@oracle.com> <01000165aa490dc9-64abf872-afd1-4a81-a46d-a50d0131de93-000000@email.amazonses.com> From: Laurent Dufour Date: Wed, 5 Sep 2018 18:17:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <01000165aa490dc9-64abf872-afd1-4a81-a46d-a50d0131de93-000000@email.amazonses.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18090516-0012-0000-0000-000002A43CA6 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18090516-0013-0000-0000-000020D85FC8 Message-Id: <839e2703-1588-0873-00a7-d04810f403cf@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-09-05_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=934 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809050166 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/09/2018 17:10, Christopher Lameter wrote: > On Tue, 4 Sep 2018, Daniel Jordan wrote: > >> - Promoting huge page usage: With memory sizes becoming ever larger, huge >> pages are becoming more and more important to reduce TLB misses and the >> overhead of memory management itself--that is, to make the system scalable >> with the memory size. But there are still some remaining gaps that prevent >> huge pages from being deployed in some situations, such as huge page >> allocation latency and memory fragmentation. > > You forgot the major issue that huge pages in the page cache are not > supported and thus we have performance issues with fast NVME drives that > are now able to do 3Gbytes per sec that are only possible to reach with > directio and huge pages. > > IMHO the huge page issue is just the reflection of a certain hardware > manufacturer inflicting pain for over a decade on its poor users by not > supporting larger base page sizes than 4k. No such workarounds needed on > platforms that support large sizes. Things just zoom along without > contortions necessary to deal with huge pages etc. > > Can we come up with a 2M base page VM or something? We have possible > memory sizes of a couple TB now. That should give us a million or so 2M > pages to work with. > >> - Reducing the number of users of mmap_sem: This semaphore is frequently >> used throughout the kernel. In order to facilitate scaling this longstanding >> bottleneck, these uses should be documented and unnecessary users should be >> fixed. > > > Large page sizes also reduce contention there. That's true for the page fault path, but for process's actions manipulating the memory process's layout (mmap,munmap,madvise,mprotect) the impact is minimal unless the code has to manipulate the page tables. >> If you haven't already done so, please let us know if you are interested in >> attending, or have suggestions for other attendees. > > Certainly interested in attending but this overlaps supercomputing 2018 in > Dallas Texas... >