From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 57E95C43613 for ; Fri, 21 Jun 2019 08:17:33 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A39F62083B for ; Fri, 21 Jun 2019 08:17:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A39F62083B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45VWkx5SLMzDqdf for ; Fri, 21 Jun 2019 18:17:29 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=lst.de (client-ip=213.95.11.211; helo=newverein.lst.de; envelope-from=hch@lst.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=lst.de Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45VWhp2WzszDqcw for ; Fri, 21 Jun 2019 18:15:36 +1000 (AEST) Received: by newverein.lst.de (Postfix, from userid 2407) id BAE6368C4E; Fri, 21 Jun 2019 10:15:01 +0200 (CEST) Date: Fri, 21 Jun 2019 10:15:01 +0200 From: Christoph Hellwig To: Linus Torvalds Subject: Re: [PATCH 16/16] mm: pass get_user_pages_fast iterator arguments in a structure Message-ID: <20190621081501.GA17718@lst.de> References: <20190611144102.8848-1-hch@lst.de> <20190611144102.8848-17-hch@lst.de> <1560300464.nijubslu3h.astroid@bobo.none> <1561032202.0qfct43s2c.astroid@bobo.none> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: sparclinux@vger.kernel.org, Rich Felker , Yoshinori Sato , Linux-sh list , Andrey Konovalov , the arch/x86 maintainers , Linux List Kernel Mailing , Nicholas Piggin , "David S. Miller" , Linux-MM , Khalid Aziz , Paul Burton , James Hogan , Paul Mackerras , linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Christoph Hellwig Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Thu, Jun 20, 2019 at 10:21:46AM -0700, Linus Torvalds wrote: > Hmm. Honestly, I've never seen anything like that in any kernel profiles. > > Compared to the problems I _do_ see (which is usually the obvious > cache misses, and locking), it must either be in the noise or it's > some problem specific to whatever CPU you are doing performance work > on? > > I've occasionally seen pipeline hiccups in profiles, but it's usually > been either some serious glass jaw of the core, or it's been something > really stupid we did (or occasionally that the compiler did: one in > particular I remember was how there was a time when gcc would narrow > stores when it could, so if you set a bit in a word, it would do it > with a byte store, and then when you read the whole word afterwards > you'd get a major pipeline stall and it happened to show up in some > really hot paths). I've not seen any difference in the GUP bench output here ar all. But I'm fine with skipping this patch for now, I have a potential series I'm looking into that would benefit a lot from it, but we can discusss it in that context and make sure all the other works gets in in time.