From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with SMTP id BC2E76B016F for ; Tue, 2 Nov 2010 10:29:33 -0400 (EDT) Received: by pwi1 with SMTP id 1so1922464pwi.14 for ; Tue, 02 Nov 2010 07:29:31 -0700 (PDT) Subject: Re: [PATCH]oom-kill: direct hardware access processes should get bonus From: "Figo.zhang" In-Reply-To: References: <1288662213.10103.2.camel@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Tue, 02 Nov 2010 22:24:54 +0800 Message-ID: <1288707894.19865.1.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: David Rientjes Cc: lkml , "linux-mm@kvack.org" , Andrew Morton List-ID: > > Which applications are you referring to that cannot gracefully exit if > killed? like Xorg server, if xorg server be killed, the gnome desktop will be crashed. > > CAP_SYS_RAWIO had a much more dramatic impact in the previous heuristic to > such a point that it would often allow memory hogging tasks to elude the > oom killer at the expense of innocent tasks. I'm not sure this is the > best way to go. is it some experiments for demonstration the CAP_SYS_RAWIO will elude the oom killer? -- 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/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org