From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [ANNOUNCE] 3.6.3-rt7
Date: Sat, 27 Oct 2012 00:08:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1210270006130.2756@ionos> (raw)
In-Reply-To: <alpine.LFD.2.02.1210262036270.2756@ionos>
On Fri, 26 Oct 2012, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.6.3-rt7 release.
>
> Changes since 3.6.3-rt6:
>
> * Enable SLUB for RT
>
> Last time I looked at SLUB for RT (some years ago) it was just
> way more painful than dealing with SLAB, but Christoph Lameter
> has done major surgery on the SLUB code since then and it turns
> out that making SLUB usable for RT has become very simple. Thanks
> Christoph!
>
> slab.c: 172 insertions(+), 58 deletions(-)
> slub.c: 17 insertions(+), 13 deletions(-)
>
> I did some quick comparisons and even a simple hackbench run
> shows a significant speedup with SLUB vs. SLAB on RT. I'm not too
> surprised as SLUBs fastpath does not have the RT induced
> contention problems which we can observe with SLAB.
>
> As usual, give it a good testing and report whatever explodes :)
Looks like CONFIG_NUMA=y exposes explosions. I just noticed that none
of the machines which are in my basic set of test systems have that
enabled.
/me goes to do some homework
next prev parent reply other threads:[~2012-10-26 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 18:52 [ANNOUNCE] 3.6.3-rt7 Thomas Gleixner
2012-10-26 22:08 ` Thomas Gleixner [this message]
2012-10-26 22:46 ` Anca Emanuel
2012-10-27 8:47 ` Thomas Gleixner
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=alpine.LFD.2.02.1210270006130.2756@ionos \
--to=tglx@linutronix.de \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).