From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with ESMTP id 936786B0044 for ; Fri, 8 Jan 2010 14:42:56 -0500 (EST) Date: Fri, 8 Jan 2010 11:42:38 -0800 (PST) From: Linus Torvalds Subject: Re: [RFC][PATCH 6/8] mm: handle_speculative_fault() In-Reply-To: Message-ID: References: <20100106115233.5621bd5e.kamezawa.hiroyu@jp.fujitsu.com> <20100106125625.b02c1b3a.kamezawa.hiroyu@jp.fujitsu.com> <1262969610.4244.36.camel@laptop> <87my0omo3n.fsf@basil.nowhere.org> <20100108192815.GB14141@basil.fritz.box> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Andi Kleen Cc: Christoph Lameter , Peter Zijlstra , KAMEZAWA Hiroyuki , Minchan Kim , "Paul E. McKenney" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "hugh.dickins" , Nick Piggin , Ingo Molnar List-ID: On Fri, 8 Jan 2010, Linus Torvalds wrote: > > Another fact is simply that you shouldn't write your app so that it needs > to do millions of page faults per second. Side note: an app with lots of threads, and that needs to fault in lots of pages at startup time, and has performance problems, can - and should - likely use interfaces that are _designed_ for that. There's things like madvise(WILLNEED) etc, which can batch up the filling of a memory area. If you're doing a performance-sensitive application with hundreds of threads, and hundreds of gigabytes of data, you had better know about simple concepts like "batch fill", rather than whine about "oh my, my totally special-case app takes a few seconds to start because I'M A F*CKING MORON AND DID EVERYTHING WRONG". Linus -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org