From: "Jeremy Linton" <jlinton@interactivesi.com>
To: "Linus Torvalds" <torvalds@transmeta.com>
Cc: "Rik van Riel" <riel@conectiva.com.br>, <linux-kernel@vger.kernel.org>
Subject: Re: [BUG][PATCH] in sys_swapoff() path
Date: Mon, 13 Aug 2001 17:18:28 -0500 [thread overview]
Message-ID: <017f01c12445$e4763520$bef7020a@mammon> (raw)
In-Reply-To: <Pine.LNX.4.33.0108101803570.1289-100000@penguin.transmeta.com>
From: "Linus Torvalds" <torvalds@transmeta.com>
> Can you test that the appended version does the same thing for you? I made
> the mm/memory.c check a bit stricter (it should be the _same_ pte entry,
...
> Plus this has Rik's swapspace full patch - fixed to NOT unconditionally
....
> Jeremy, Rik, please verify my changes..
Looks good!!! I grabbed 2.4.8 and put it on my machine, closely inspected
your changes to my original patch and quickly took a look at Rik's code.
They both look fine and my tests seem to prove that they are. On the other
hand, the swapoff times are slower than 2.4.7pre6 with my patches applied, I
assume that is probably something else in the kernel. This kernel version
also has some problems running the stress program that helped to find those
bugs originally. Now when it is running, xosview 'bails' out with a "Can not
open file: /proc/interrupts" or similar message after a couple minutes of
steady thrashing.
If I get a chance, I will look at the xosview problems as well as some of
the other strange behaviors.
jlinton
prev parent reply other threads:[~2001-08-13 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 23:59 [BUG][PATCH] in sys_swapoff() path Jeremy Linton
2001-08-11 1:08 ` Linus Torvalds
2001-08-11 1:13 ` Rik van Riel
2001-08-13 22:18 ` Jeremy Linton [this message]
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='017f01c12445$e4763520$bef7020a@mammon' \
--to=jlinton@interactivesi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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