public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Robert Love <rml@tech9.net>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preempt-kernel on 2.4.19-pre2-ac2 bugfix
Date: Thu, 7 Mar 2002 15:21:05 -0800	[thread overview]
Message-ID: <20020307232105.GD28141@matchmail.com> (raw)
In-Reply-To: <1015287791.882.25.camel@phantasy>
In-Reply-To: <1015287791.882.25.camel@phantasy>

On Mon, Mar 04, 2002 at 07:23:10PM -0500, Robert Love wrote:
> The same schedule_tail bug affecting 2.5 affects 2.4 with O(1).  I.e.,
> 2.4.19-pre2-ac2.
> 
> In recent O(1) scheduler releases, an optimization was made that removed
> schedule_tail from UP kernels.  This causes the initial preempt_count of
> a new task, which starts at 1, to never decrement to zero and thus never
> become preemptible.  CONFIG_PREEMPT requires schedule_tail, too.
> 
> Users of 2.4+O(1)+preempt (i.e. -ac) should use this patch:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/preempt-kernel-rml-2.4.19-pre2-ac2-2.patch
> 

I'm using 2.4.19-pre2-ac2-prmpt which is only patched with:
preempt-kernel-rml-2.4.19-pre2-ac2-3

And it looks like the VM accounting has been messed up.

        total:    used:    free:  shared: buffers:  cached:
Mem:  129662976 99065856 30597120        0  5013504 69664768
Swap: 500056064 97660928 402395136
MemTotal:       126624 kB
MemFree:         29880 kB
MemShared:           0 kB
Buffers:          4896 kB
Cached:          33188 kB
SwapCached:      34844 kB
Active:          62536 kB
Inact_dirty:     20328 kB
Inact_clean:       876 kB
Inact_target:    16748 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       126624 kB
LowFree:         29880 kB
SwapTotal:      488336 kB
SwapFree:       392964 kB
Committed AS:   366712 kB

As you can see, it says I'm using 366MB (roughly) of ram, but I'm only about
95mb into swap with 128mb of ram.

Alan, do you want me to try without preempt, or do you already have any
other reports like this?

The kernel is compiled smp, but this machine is UP.  I can post .config and
other info if needed just ask.

Mike

  parent reply	other threads:[~2002-03-07 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  0:23 [PATCH] preempt-kernel on 2.4.19-pre2-ac2 bugfix Robert Love
2002-03-05  0:41 ` Mike Fedyk
2002-03-05  0:52   ` Robert Love
2002-03-07 23:21 ` Mike Fedyk [this message]
2002-03-07 23:46   ` Alan Cox
2002-03-08  0:05     ` Mike Fedyk
2002-03-08  0:38       ` Alan Cox
2002-03-08  2:27         ` Mike Fedyk
2002-03-08 13:21           ` Alan Cox
2002-03-08 19:26             ` Mike Fedyk
2002-03-09 23:35               ` Mike Fedyk
2002-03-10  0:53                 ` Alan Cox

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=20020307232105.GD28141@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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