From: Arjan van de Ven <arjan@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: Patch series to mark struct file_operations and struct inode_operations const
Date: Sat, 13 Jan 2007 16:51:08 -0800 [thread overview]
Message-ID: <1168735868.3123.315.camel@laptopd505.fenrus.org> (raw)
Hi,
today a sizable portion of the "struct file_operations" variables in the
kernel are const, but by far not all. Nor are any of the struct
inode_operations const. Marking these read-only datastructures const has
the advantage of reducing false sharing of these, often hot,
datastructures. In addition there have been cases where drivers or
filesystems accidentally and incorrectly wrote to such a struct
forgetting that it's a shared datastructure. By marking these const, the
compiler will warn/error on such instances.
The series is split up for size, there isn't really any logical order
for such a simple search-and-replace operation.
Greetings,
Arjan van de Ven
next reply other threads:[~2007-01-14 0:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 0:51 Arjan van de Ven [this message]
2007-01-14 0:51 ` [patch 00/12] Fix ppc64's writing to struct file_operations Arjan van de Ven
2007-01-14 14:54 ` Alan
2007-01-14 23:55 ` Stephen Rothwell
2007-01-15 0:15 ` Arjan van de Ven
2007-01-14 0:52 ` [patch 01/12] mark struct file_operations const 1 Arjan van de Ven
2007-01-14 0:53 ` [patch 02/12] mark struct file_operations const 2 Arjan van de Ven
2007-01-14 0:53 ` [patch 03/12] mark struct file_operations const 3 Arjan van de Ven
2007-01-14 0:54 ` [patch 04/12] mark struct file_operations const 4 Arjan van de Ven
2007-01-14 0:54 ` [patch 05/12] mark struct file_operations const 5 Arjan van de Ven
2007-01-14 0:55 ` [patch 06/12] mark struct file_operations const 6 Arjan van de Ven
2007-01-14 0:56 ` [patch 07/12] mark struct file_operations const 7 Arjan van de Ven
2007-01-14 0:56 ` [patch 08/12] mark struct file_operations const 8 Arjan van de Ven
2007-01-14 0:57 ` [patch 09/12] mark struct file_operations const 9 Arjan van de Ven
2007-01-14 0:57 ` [patch 10/12] mark struct inode_operations const 1 Arjan van de Ven
2007-01-14 0:58 ` [patch 11/12] mark struct inode_operations const 2 Arjan van de Ven
2007-01-14 0:58 ` [patch 12/12] mark struct inode_operations const 3 Arjan van de Ven
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=1168735868.3123.315.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®