[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091202095012.GD22654@elte.hu>
Date: Wed, 2 Dec 2009 10:50:12 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...hat.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-kernel@...r.kernel.org, dhowells@...hat.com,
hidehiro.kawai.ez@...achi.com, lethal@...ux-sh.org,
roland@...hat.com, vapier@...too.org,
Takahiro Yasui <tyasui@...hat.com>
Subject: Re: [PATCH v2] mm: Introduce coredump parameter structure
* Masami Hiramatsu <mhiramat@...hat.com> wrote:
> Andrew Morton wrote:
> >On Sat, 28 Nov 2009 23:41:19 -0500
> >Masami Hiramatsu<mhiramat@...hat.com> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists