[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1409190637190.2507@hadrien>
Date: Fri, 19 Sep 2014 06:45:51 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: "Drokin, Oleg" <oleg.drokin@...el.com>
cc: Dan Carpenter <dan.carpenter@...cle.com>,
"<devel@...verdev.osuosl.org>" <devel@...verdev.osuosl.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"<kernel-janitors@...r.kernel.org>" <kernel-janitors@...r.kernel.org>,
"<linux-kernel@...r.kernel.org>" <linux-kernel@...r.kernel.org>,
Julia Lawall <Julia.Lawall@...6.fr>,
"<HPDD-discuss@...1.01.org>" <HPDD-discuss@...1.01.org>
Subject: Re: [HPDD-discuss] [PATCH] staging: lustre: llite: Use kzalloc and
rewrite null tests
With respect to the upper case lower case issue, does the thing need to be
a macro? I think that the lowercase is more or less fine, but only if
what is behind it is a function.
I say more or less fine, because normally in the kernel the special
allocators have special purposes, eg allocating and initializing the xyz
structure. Here what is wanted is a general purpose allocator with lots
of special tracing features, so it is not quite the same thing. And one
can wonder why all of these special tracing features are not relevant to
the kernel as a whole?
In reading through the description of the needed features, it seems like
only the _ptr extension requires being a macro. Do we need that? The
rest of the kernel manages to do x = kzalloc(sizeof(*x),...) ok. It's
unpleasant to have an assignment hidden in this way. And currently it is
not used consistently. There are some OBD_ALLOCs that have the same form.
Sorry for overlooking the frees. I was focusing on trying one thing at a
time...
julia
--
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