Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755313AbbGPKCY (ORCPT ); Thu, 16 Jul 2015 06:02:24 -0400 Received: from mx2.parallels.com ([199.115.105.18]:52004 "EHLO mx2.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754599AbbGPKCW (ORCPT ); Thu, 16 Jul 2015 06:02:22 -0400 Date: Thu, 16 Jul 2015 13:02:11 +0300 From: Vladimir Davydov To: Andres Lagar-Cavilla CC: Andrew Morton , Minchan Kim , Raghavendra K T , Johannes Weiner , Michal Hocko , Greg Thelen , Michel Lespinasse , David Rientjes , Pavel Emelyanov , Cyrill Gorcunov , Jonathan Corbet , , , , , Subject: Re: [PATCH -mm v8 0/7] idle memory tracking Message-ID: <20150716100211.GC2001@esperanza> References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: X-Originating-IP: [10.30.4.177] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1126 Lines: 29 On Wed, Jul 15, 2015 at 01:47:15PM -0700, Andres Lagar-Cavilla wrote: > I think the remaining question here is performance. > > Have you conducted any studies where > - there is a workload > - a daemon is poking kpageidle every N seconds/minutes > - what is the daemon cpu consumption? > - what is the workload degradation if any? > > N candidates include 30 seconds, 1 minute, 2 minutes, 5 minutes.... > > Workload candidates include TPC, spec int memory intensive things like > 429.mcf, stream (http://www.cs.virginia.edu/stream/ "sustainable > memory bandwidth" vs floating point performance) > > I'm not asking for a research paper, but if, say, a 2 minute-period > daemon introduces no degradation and adds up to a minute of cpu per > hour, then we're golden. Fair enough. Will do that soon and report back. Thanks a lot for the review, it was really helpful! Vladimir -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/