All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Emese Revfy <re.emese@gmail.com>
Cc: mingo@redhat.com, tglx@linutronix.de,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Constify struct mtrr_ops for v2.6.33-rc6
Date: Mon, 01 Feb 2010 11:08:26 -0800	[thread overview]
Message-ID: <4B6726AA.4000009@zytor.com> (raw)
In-Reply-To: <4B65D712.3080804@gmail.com>

On 01/31/2010 11:16 AM, Emese Revfy wrote:
> From: Emese Revfy <re.emese@gmail.com>
> 
> Constify struct mtrr_ops.
> 
> This is part of the ops structure constification
> effort started by Arjan van de Ven et al.
> 
> Benefits of this constification:
> 
>  * prevents modification of data that is shared
>    (referenced) by many other structure instances
>    at runtime
> 
>  * detects/prevents accidental (but not intentional)
>    modification attempts on archs that enforce
>    read-only kernel data at runtime
> 
>  * potentially better optimized code as the compiler
>    can assume that the const data cannot be changed
> 
>  * the compiler/linker move const data into .rodata
>    and therefore exclude them from false sharing
> 
> Signed-off-by: Emese Revfy <re.emese@gmail.com>
> Acked-by: H. Peter Anvin <hpa@zytor.com>

Yes, but this doesn't exactly seem like 2.6.33 matter.  I will put it in
-tip for 2.6.34.

	-hpa

       reply	other threads:[~2010-02-01 19:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B65D712.3080804@gmail.com>
2010-02-01 19:08 ` H. Peter Anvin [this message]
2010-02-01 19:54 ` [tip:x86/mtrr] x86, mtrr: Constify struct mtrr_ops tip-bot for Emese Revfy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B6726AA.4000009@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=re.emese@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.