public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Emese Revfy <re.emese@gmail.com>
Cc: lenb@kernel.org, bjorn.helgaas@hp.com, jbarnes@virtuousgeek.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Constify struct acpi_dock_ops for v2.6.33-rc6
Date: Thu, 04 Feb 2010 01:13:18 -0500	[thread overview]
Message-ID: <4B6A657E.4050408@pobox.com> (raw)
In-Reply-To: <4B65D72B.8070000@gmail.com>

On 01/31/2010 02:16 PM, Emese Revfy wrote:
> From: Emese Revfy<re.emese@gmail.com>
>
> Constify struct acpi_dock_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>
> ---
>
>   drivers/acpi/dock.c                |    4 ++--
>   drivers/ata/libata-acpi.c          |    4 ++--
>   drivers/pci/hotplug/acpiphp_glue.c |    2 +-
>   include/acpi/acpi_drivers.h        |    4 ++--
>   4 files changed, 7 insertions(+), 7 deletions(-)

Acked-by: Jeff Garzik <jgarzik@redhat.com>



           reply	other threads:[~2010-02-04  6:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4B65D72B.8070000@gmail.com>]

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=4B6A657E.4050408@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@linux-foundation.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=re.emese@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox