From: Tejun Heo <tj@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] slab fixes for 3.2-rc4
Date: Thu, 22 Dec 2011 08:08:22 -0800 [thread overview]
Message-ID: <20111222160822.GE17084@google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1112220854440.31315@router.home>
Hello, Christoph.
On Thu, Dec 22, 2011 at 08:58:43AM -0600, Christoph Lameter wrote:
> Well that would be a pretty nice simplification of the API.
> Replace the fallback code for the preempt safe ones with the
> irqsafe fallbacks, then drop the irqsafe variants from percpu.h.
Yeah, it seems we're going that direction.
> > > The way that the cmpxchg things are used is also similar to transactional
> > > memory that is becoming available in the next generation of processors by
> > > Intel and that is already available in the current generation of powerpc
> > > processors by IBM. It is a way to avoid locking overhead.
> >
> > Hmmm... how about removing the ones which aren't currently in use?
>
> Yep. Could easily be done. We can resurrect the stuff as needed when other
> variants become necessary. In particular the _and and _or etc stuff was
> just added to be backward compatible with the old per cpu and local_t
> interfaces. There may be no use cases left.
Yeap, and that one too. Maybe we can finally kill the duplicate
confusing static/dynamic accessors too. I'm planning to get to it in
several weeks but if anyone can beat me to it, please go ahead.
Thank you.
--
tejun
next prev parent reply other threads:[~2011-12-22 16:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.02.1111292001420.4019@tux.localdomain>
2011-11-29 19:29 ` [GIT PULL] slab fixes for 3.2-rc4 Linus Torvalds
2011-11-29 19:38 ` Linus Torvalds
2011-11-29 19:38 ` Linus Torvalds
2011-12-20 9:47 ` Pekka Enberg
2011-12-20 16:23 ` Tejun Heo
2011-12-20 16:31 ` Christoph Lameter
2011-12-20 16:31 ` Christoph Lameter
2011-12-20 19:28 ` Linus Torvalds
2011-12-20 20:28 ` Tejun Heo
2011-12-21 8:08 ` Pekka Enberg
2011-12-21 17:09 ` Tejun Heo
2011-12-21 15:16 ` Christoph Lameter
2011-12-21 17:05 ` Tejun Heo
2011-12-22 2:19 ` Linus Torvalds
2011-12-22 16:05 ` Tejun Heo
2011-12-28 10:25 ` Benjamin Herrenschmidt
2011-12-22 14:58 ` Christoph Lameter
2011-12-22 14:58 ` Christoph Lameter
2011-12-22 16:08 ` Tejun Heo [this message]
2011-12-22 17:58 ` Christoph Lameter
2011-12-22 18:03 ` Ingo Molnar
2011-12-22 18:31 ` Linus Torvalds
2011-12-23 16:55 ` Christoph Lameter
2011-12-23 20:54 ` Linus Torvalds
2012-01-04 15:30 ` Christoph Lameter
2012-01-04 16:07 ` Linus Torvalds
2012-01-04 17:00 ` Christoph Lameter
2012-01-04 23:10 ` Linus Torvalds
2012-01-04 23:10 ` Linus Torvalds
2012-01-05 19:15 ` Christoph Lameter
2012-01-05 19:27 ` Linus Torvalds
2011-12-22 18:47 ` Tejun Heo
2011-12-20 16:26 ` Christoph Lameter
2011-12-20 16:26 ` Christoph Lameter
2011-12-21 8:06 ` Pekka Enberg
2011-12-21 15:20 ` 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=20111222160822.GE17084@google.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).