public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Gregory Haskins <ghaskins@novell.com>,
	jim.houston@ccur.com, joe.korty@ccur.com, rostedt@goodmis.org,
	tglx@linutronix.de, dwalker@mvista.com,
	David Bahi <DBahi@novell.com>, Moiz Kohari <MKohari@novell.com>,
	Sven Dietrich <SDietrich@novell.com>,
	dsaxena@plexity.net, williams@redhat.com, abogani@texware.it,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available
Date: Sat, 14 Jul 2007 10:27:01 +1000	[thread overview]
Message-ID: <46981855.8040904@bigpond.net.au> (raw)
In-Reply-To: <200707130443.11356.gene.heskett@gmail.com>

Gene Heskett wrote:
> On Friday 13 July 2007, Peter Williams wrote:
>> Ingo Molnar wrote:
>>> * Gregory Haskins <ghaskins@novell.com> wrote:
>>>> On Thu, 2007-07-12 at 14:07 +0200, Ingo Molnar wrote:
>>>>> * Gregory Haskins <ghaskins@novell.com> wrote:
>>>>>> Hi Ingo, Thomas, and the greater linux-rt community,
>>>>>>
>>>>>> 	I just wanted to let you guys know that our team has a port of
>>>>>> the 21.5-rt20 patch for the 2.6.22 kernel available. [...]
>>>>> great! We had the upstream -rt port to .22 in the works too, it was just
>>>>> held up by the hpet breakage - which Thomas managed to fix earlier
>>>>> today. I've released the 2.6.22.1-rt1 patch to the usual place:
>>>>>
>>>>>     http://redhat.com/~mingo/realtime-preempt/
>>>> Thats awesome, Ingo!  Thanks!  Could you publish a broken out version
>>>> as well?  We found it extremely valuable to be able to bisect this
>>>> beast while working on the 21-22 port.
>>> we are working on something in this area :) Stay tuned ...
>> I've just been reviewing these patches and have spotted an error in the
>> file mm/slob.c at lines 500-501 whereby a non existent variable "c" is
>> referenced.  The attached patch is a proposed fix to the problem.
> 
> Could this explain why 2.6.22.1-rt1 seems to use a lot of swap?  I've been as 
> high as 570 megs into swap, currently at 286megs after doing a 
> swapoff --a;swapon -a about 8 hours ago.

No.  This problem would have caused the build to fail if slob was
configured.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
 -- Ambrose Bierce

  parent reply	other threads:[~2007-07-14  1:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 12:26 Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available Gregory Haskins
2007-07-12 13:09 ` Ingo Molnar
2007-07-13  6:25   ` Peter Williams
2007-07-13  6:52     ` Thomas Gleixner
2007-07-13  8:43     ` Gene Heskett
2007-07-13  9:42       ` Thomas Gleixner
2007-07-14  0:27       ` Peter Williams [this message]
2007-07-14  0:52         ` Gene Heskett
2007-07-26  1:24   ` Minor errors in 2.6.23-rc1-rt2 series Peter Williams
2007-07-26  7:36     ` Ingo Molnar
2007-08-06  1:29   ` Possible error in 2.6.23-rc2-rt1 series Peter Williams
2007-08-06  5:42     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2007-07-12 16:26 Forward port of latest RT patch (2.6.21.5-rt20) to 2.6.22 available Gregory Haskins
2007-07-12 16:33 ` Ingo Molnar
2007-07-12 20:21   ` Sven-Thorsten Dietrich
2007-07-13 12:52   ` Benjamin Herrenschmidt
2007-07-12 11:10 Gregory Haskins
2007-07-12 10:17 Gregory Haskins
2007-07-12  0:58 Gregory Haskins
2007-07-12  1:05 ` Daniel Walker
2007-07-12  5:14 ` Thomas Gleixner
2007-07-12  7:27 ` Alessio Igor Bogani
2007-07-12 12:07 ` Ingo Molnar

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=46981855.8040904@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=DBahi@novell.com \
    --cc=MKohari@novell.com \
    --cc=SDietrich@novell.com \
    --cc=abogani@texware.it \
    --cc=dsaxena@plexity.net \
    --cc=dwalker@mvista.com \
    --cc=gene.heskett@gmail.com \
    --cc=ghaskins@novell.com \
    --cc=jim.houston@ccur.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    /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