Re: [PATCH] revert to static = {0}

From: Arjan van de Ven (arjanv@redhat.com)
Date: Tue Aug 05 2003 - 11:07:17 EST

Next message: Ducrot Bruno: "Re: [TRIVIAL] sanitize power management config menus, take two"
Previous message: Marc Heckmann: "2.4.22-pre9, 8139too driver: eth0: Too much work at interrupt"
In reply to: Hugh Dickins: "[PATCH] revert to static = {0}"
Next in thread: Hugh Dickins: "[PATCH] revert to static = {0} + comment"
Reply: Hugh Dickins: "[PATCH] revert to static = {0} + comment"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 2003-08-05 at 17:48, Hugh Dickins wrote:
> Please revert to static zero initialization of a const: when thus
> initialized it's linked into a readonly cacheline shared between cpus;
> otherwise it's linked into bss, likely to be in a dirty cacheline
> bouncing between cpus.

how about adding a big fat comment here that says this?
Otherwise this keeps happening all the time...

application/pgp-signature attachment: This is a digitally signed message part

-
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/

Next message: Ducrot Bruno: "Re: [TRIVIAL] sanitize power management config menus, take two"
Previous message: Marc Heckmann: "2.4.22-pre9, 8139too driver: eth0: Too much work at interrupt"
In reply to: Hugh Dickins: "[PATCH] revert to static = {0}"
Next in thread: Hugh Dickins: "[PATCH] revert to static = {0} + comment"
Reply: Hugh Dickins: "[PATCH] revert to static = {0} + comment"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:29 EST