From: Christoph Lameter <cl@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Tejun Heo <tj@kernel.org>
Cc: Mike Frysinger <vapier.adi@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC local_t removal V2 0/3] Remove local_t
Date: Thu, 07 Jan 2010 16:35:24 -0600 [thread overview]
Message-ID: <20100107223524.760517016@quilx.com> (raw)
Current -next has only the trace subsystem left as a user of local_t
Tracing uses local_t for per cpu safe atomic operations in the form
of cmpxchg and additions.
This patchset removes unused function in local.h and then genericizes
local.h by removing local_t. This results in a very small set of
functions.
"long" is used for now instead of local_t. With some additional work it
would be possible to pass arbitrary types to local_xx() function like
cmpxchg_local() and the this_cpu_xx() functions. Maybe a more flexible
way of handling local_xx() would allow the use of these functions in
other kernel subsystems.
Still RFC state. Lots of stuff todo. Compiles on my box.
V1->V2
- Preserve local.h
- Add a rationale why the remaining functions are useful and how
they differ from this_cpu_xx.
next reply other threads:[~2010-01-07 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 22:35 Christoph Lameter [this message]
2010-01-07 22:35 ` [RFC local_t removal V2 1/3] Remove unused local.h functions Christoph Lameter
2010-01-07 22:35 ` [RFC local_t removal V2 2/3] Remove local_t type from tree Christoph Lameter
2010-01-08 8:55 ` Arnd Bergmann
2010-01-07 22:35 ` [RFC local_t removal V2 3/3] Eliminate local_cmpxchg Christoph Lameter
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=20100107223524.760517016@quilx.com \
--to=cl@linux-foundation.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=tj@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
Powered by JetHome