From: Thomas Gleixner <tglx@linutronix.de>
To: Madovsky <infos@madovsky.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rc7-rt0
Date: Wed, 20 Jul 2011 17:56:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1107201753220.2702@ionos> (raw)
In-Reply-To: <CCEC72C697934346AA1E7D01E8DA2EF5@e1705>
Franck,
On Wed, 20 Jul 2011, Madovsky wrote:
> Hi Thomas,
>
> I just compiled the kernel with the patch on my whole cluster
> of 6 fedora10 and the results are very stable and smooth.
Thanks for the report !
> the only little thing is the cluster software heartbeat / pacemaker
> takes 20% of cpu that 11% before on a dual xeon nocona with
> linux command "top".
That might be related to the new mechanism how we handle softirqs. If
the heartbeat/pacemaker app is using networking a lot then this might
explain it.
Thanks,
tglx
next prev parent reply other threads:[~2011-07-20 15:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 0:37 [ANNOUNCE] 3.0-rc7-rt0 Thomas Gleixner
2011-07-20 2:48 ` Frank Rowand
2011-07-20 3:22 ` Fernando Lopez-Lezcano
2011-07-20 5:03 ` Paul E. McKenney
2011-07-20 9:02 ` David Kastrup
2011-07-20 9:02 ` David Kastrup
2011-07-20 9:48 ` Geunsik Lim
2011-07-20 9:48 ` Geunsik Lim
2011-07-20 11:08 ` Armin Steinhoff
2011-07-20 15:33 ` Madovsky
2011-07-20 15:56 ` Thomas Gleixner [this message]
2011-07-20 15:59 ` Madovsky
2011-07-20 17:02 ` Darren Hart
2011-07-20 18:35 ` [ANNOUNCE] 3.0-rc7-rt0 (hang then panic on dual socket xeon) Darren Hart
2011-07-20 19:10 ` [PATCH] Fix build failure for modular ext3/4 builds Uwe Kleine-König
2011-07-20 19:15 ` [ANNOUNCE] 3.0-rc7-rt0 Noah Watkins
-- strict thread matches above, loose matches on Subject: below --
2011-07-21 16:22 hermann
2011-07-21 17:35 ` Thomas Gleixner
2011-07-21 17:43 ` Thomas Gleixner
2011-07-21 18:33 ` hermann
2011-07-21 18:28 ` andi
2011-07-21 18:40 ` hermann
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.1107201753220.2702@ionos \
--to=tglx@linutronix.de \
--cc=infos@madovsky.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.