From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263103AbUKTEJ4 (ORCPT ); Fri, 19 Nov 2004 23:09:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263125AbUKTEFS (ORCPT ); Fri, 19 Nov 2004 23:05:18 -0500 Received: from smtp203.mail.sc5.yahoo.com ([216.136.129.93]:25271 "HELO smtp203.mail.sc5.yahoo.com") by vger.kernel.org with SMTP id S263111AbUKTEDW (ORCPT ); Fri, 19 Nov 2004 23:03:22 -0500 Message-ID: <419EC205.5030604@yahoo.com.au> Date: Sat, 20 Nov 2004 15:03:17 +1100 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040820 Debian/1.7.2-4 X-Accept-Language: en MIME-Version: 1.0 To: William Lee Irwin III CC: Linus Torvalds , Christoph Lameter , akpm@osdl.org, Benjamin Herrenschmidt , Hugh Dickins , linux-mm@kvack.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: page fault scalability patch V11 [0/7]: overview References: <419D581F.2080302@yahoo.com.au> <419D5E09.20805@yahoo.com.au> <1100848068.25520.49.camel@gaston> <20041120020306.GA2714@holomorphy.com> <419EBBE0.4010303@yahoo.com.au> <20041120035510.GH2714@holomorphy.com> In-Reply-To: <20041120035510.GH2714@holomorphy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org William Lee Irwin III wrote: > William Lee Irwin III wrote: > >>>Unprivileged triggers for full-tasklist scans are NMI oops material. > > > On Sat, Nov 20, 2004 at 02:37:04PM +1100, Nick Piggin wrote: > >>Hang on, let's come back to this... >>We already have unprivileged do-for-each-thread triggers in the proc >>code. It's in do_task_stat, even. Rss reporting would basically just >>involve one extra addition within that loop. >>So... hmm, I can't see a problem with it. > > > /proc/ triggering NMI oopses was a persistent problem even before that > code was merged. I've not bothered testing it as it at best aggravates it. > It isn't a problem. If it ever became a problem then we can just touch the nmi oopser in the loop. > And thread groups can share mm's. do_for_each_thread() won't suffice. > I think it will be just fine.