From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753351AbZLBJu2 (ORCPT ); Wed, 2 Dec 2009 04:50:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751192AbZLBJu1 (ORCPT ); Wed, 2 Dec 2009 04:50:27 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:41082 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072AbZLBJu1 (ORCPT ); Wed, 2 Dec 2009 04:50:27 -0500 Date: Wed, 2 Dec 2009 10:50:12 +0100 From: Ingo Molnar To: Masami Hiramatsu Cc: Andrew Morton , Oleg Nesterov , KOSAKI Motohiro , linux-kernel@vger.kernel.org, dhowells@redhat.com, hidehiro.kawai.ez@hitachi.com, lethal@linux-sh.org, roland@redhat.com, vapier@gentoo.org, Takahiro Yasui Subject: Re: [PATCH v2] mm: Introduce coredump parameter structure Message-ID: <20091202095012.GD22654@elte.hu> References: <200911202212.nAKMCF2v012068@imap1.linux-foundation.org> <20091126174835.5A73.A69D9226@jp.fujitsu.com> <4B0EA3AA.5070003@redhat.com> <20091126165108.GA13231@redhat.com> <4B11FB6F.4040403@redhat.com> <20091201161800.fa6b6ae4.akpm@linux-foundation.org> <4B15B4ED.8010209@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B15B4ED.8010209@redhat.com> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Masami Hiramatsu wrote: > Andrew Morton wrote: > >On Sat, 28 Nov 2009 23:41:19 -0500 > >Masami Hiramatsu wrote: > > > >>Introduce coredump parameter data structure (struct coredump_params) > >>for simplifying binfmt->core_dump() arguments. > >> > >>Changes in v2: > >> - Don't remove DUMP_WRITE() macro. > > > >What is the reason for this change? > > > >Please always include both the "what" and the "why" in changelog text. > > I see. I think Andrew wanted to see a longer explanation about precisely what we need for these tracepoints and what the various specific usecases are to utilize it. I.e. a basic cost/benefit analysis is needed. By looking at the patch we can see the cost - but you have to counter-balance that with enough stuff in the 'benefits' column of the equation. Ingo