Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp415623img; Mon, 18 Mar 2019 06:09:30 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmSucwS5FcQSk4LHBb3bzNPJx+mOZVH1XYOIfruG9L//DDpK8NiYIy39NEETKYxT3RcLV2 X-Received: by 2002:a63:5452:: with SMTP id e18mr9707972pgm.386.1552914569990; Mon, 18 Mar 2019 06:09:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552914569; cv=none; d=google.com; s=arc-20160816; b=PQP99Q8iIxJC/8Kxy5fQMU3nH7r97AsUyMd/7xibpemJpy7vpSKGfh64HMnBRpi7qv TVatDgzddcPSGyiTc4ZIYAViLslpXkn5czgRwjoPnIQ7WnegdrRQlEH/70HW+Ec3neIi pxFt9I5u4D0K/isWWvlMjxGFhXGiyUBjcnI7BdbL48j2DH0B/5UHgmM6uE+p/YcQdFfr pwIDMf2CF7UASuZI7NAgbkx6nj+Thu+Uvkp8QZJHmXu1bK3mEXxBjRHfdoz8pWwYHRwv FXcyHo0gpV6ncZ3tmuZRV+Th4JzqJzU0yudgahWRcBXsw8re7jY1ulYzYozZJ6di+SXT Zizg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=EtABQaRkoJ28tVLnbJea5RT6bU0rAHDKiH3UUaBPD8Y=; b=RaU5BArMjz3zhn8C6te5a4UMDPCKimVqxP6CGE8yBwpcU2AEqufp2CCH9QSdZ/Dqkw BqdiAtmd5k4Umqk/W8/xTHGNS3v1e+YS6VwN/gSELgaMs2Nc/rZ0A+DE0HpyGBdifSLt 3+BWMBlrCJuSbpONQ2ZM4ERB0XbR54BXsAWal2CtqhaCnsqrYm4mZyyf+2xftexXG1Xl jcMbvs+EVHYgyRgk8+UM54G4mxONg+B6sLD5zQhHnQhQv6skfGoHuop3oIkwoi7fyP2w KpIN3DV1a1rPTnH1UfKXpCJQAUWsERbURoBp3wM5g02grS37IDF7O6fxkJWm7Gqu18Ct a9YA== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r7si8902290pgi.20.2019.03.18.06.09.14; Mon, 18 Mar 2019 06:09:29 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbfCRNIA (ORCPT + 99 others); Mon, 18 Mar 2019 09:08:00 -0400 Received: from mx2.suse.de ([195.135.220.15]:38468 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725973AbfCRNH7 (ORCPT ); Mon, 18 Mar 2019 09:07:59 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 92E7DAE07; Mon, 18 Mar 2019 13:07:58 +0000 (UTC) Date: Mon, 18 Mar 2019 14:07:57 +0100 From: Michal Hocko To: Pankaj Suryawanshi Cc: "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "minchan@kernel.org" , Kirill Tkhai Subject: Re: mm/cma.c: High latency for cma allocation Message-ID: <20190318130757.GG8924@dhcp22.suse.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 18-03-19 12:58:28, Pankaj Suryawanshi wrote: > Hello, > > I am facing issue of high latency in CMA allocation of large size buffer. > > I am frequently allocating/deallocation CMA memory, latency of allocation is very high. > > Below are the stat for allocation/deallocation latency issue. > > (390100 kB), latency 29997 us > (390100 kB), latency 22957 us > (390100 kB), latency 25735 us > (390100 kB), latency 12736 us > (390100 kB), latency 26009 us > (390100 kB), latency 18058 us > (390100 kB), latency 27997 us > (16 kB), latency 560 us > (256 kB), latency 280 us > (4 kB), latency 311 us > > I am using kernel 4.14.65 with android pie(9.0). > > Is there any workaround or solution for this(cma_alloc latency) issue ? Do you have any more detailed information on where the time is spent? E.g. migration tracepoints? -- Michal Hocko SUSE Labs