Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753625Ab2KLW2V (ORCPT ); Mon, 12 Nov 2012 17:28:21 -0500 Received: from mail-pa0-f46.google.com ([209.85.220.46]:49687 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752663Ab2KLW2U (ORCPT ); Mon, 12 Nov 2012 17:28:20 -0500 Date: Mon, 12 Nov 2012 14:28:17 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Thiago Farina cc: Michal Hocko , Andrew Morton , KAMEZAWA Hiroyuki , KOSAKI Motohiro , Greg Kroah-Hartman , Anton Vorontsov , Oleg Nesterov , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch 2/2] mm, oom: fix race when specifying a thread as the oom origin In-Reply-To: Message-ID: References: <20121108155112.GN31821@dhcp22.suse.cz> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 602 Lines: 14 On Mon, 12 Nov 2012, Thiago Farina wrote: > > I didn't like the previous playing with the oom_score_adj and what you > > propose looks much nicer. > > Maybe s/oom_task_origin/task_oom_origin/ would be a better fit > May be s/oom_task_origin/is_task_origin_oom? Just my 2 cents. > I like to prefix oom killer functions in the global namespace with "oom_" -- 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/