[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150430184232.GG5117@pd.tnic>
Date: Thu, 30 Apr 2015 20:42:32 +0200
From: Borislav Petkov <bp@...e.de>
To: "Luis R. Rodriguez" <mcgrof@...e.com>
Cc: Kyle McMartin <kyle@...nel.org>, Christoph Lameter <cl@...ux.com>,
Alok N Kataria <alokk@...softinc.com>,
Shobhit Dayal <shobhit@...softinc.com>,
Shai Fultheim <shai@...lex86.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@...not-panic.com>, mingo@...e.hu,
tglx@...utronix.de, hpa@...or.com, plagnioj@...osoft.com,
tomi.valkeinen@...com, daniel.vetter@...el.com, airlied@...ux.ie,
dledford@...hat.com, awalls@...metrocast.net, syrjala@....fi,
luto@...capital.net, mst@...hat.com, cocci@...teme.lip6.fr,
linux-kernel@...r.kernel.org, Juergen Gross <jgross@...e.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Dave Airlie <airlied@...hat.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org
Subject: Re: [PATCH v4 2/8] init.h: add __read_mostly to early_param_on_off()
On Thu, Apr 30, 2015 at 08:32:00PM +0200, Luis R. Rodriguez wrote:
> In this particular case early_param_on_off() will be used for boot
> time kernel parameters which we do not intend on dynamically change a
> lot at run time, we
It is not about whether you're going to dynamically change it but more
about how often it is accessed. If it is accessed only a couple of times
tops during boot and then never again during the system lifetime - which
is generally the case for most boot params - then you certainly don't
want to pollute the read.mostly section with dead weight. You can just
as well use a stinking normal variable.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
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