From: Andy Lutomirski <luto@myrealbox.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Bernd Eckenfels <ecki-news2004-05@lina.inka.de>,
linux-kernel@vger.kernel.org
Subject: Re: MM patches (was Re: why swap at all?)
Date: Mon, 31 May 2004 10:34:32 -0700 [thread overview]
Message-ID: <40BB6CA8.9070307@myrealbox.com> (raw)
In-Reply-To: <40B84C85.8010207@yahoo.com.au>
Nick Piggin wrote:
> Yep.
>
> Thanks to everyone's input I was able to test and adapt my mm work.
> It is hopefully at a stage where it can have wider testing now. It
> is stable on my SMP system under very heavy swapping, but the usual
> caution applies.
Thanks!
This feels quite a bit better on my system. I'll try and stress it a bit
more later today or tomorrow, but my system is now usable under heavy io load.
--Andy
next prev parent reply other threads:[~2004-05-31 17:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fegqf9v.kmidof@ifi.uio.no>
[not found] ` <fa.bqpvcrs.u648jq@ifi.uio.no>
2004-05-27 11:39 ` why swap at all? Andy Lutomirski
2004-05-28 21:37 ` Denis Vlasenko
2004-05-28 22:28 ` Bernd Eckenfels
2004-05-29 7:31 ` Denis Vlasenko
2004-05-29 8:40 ` MM patches (was Re: why swap at all?) Nick Piggin
2004-05-29 8:46 ` Nick Piggin
[not found] ` <200405292014.23559.matt@lpbproductions.com>
2004-05-30 3:31 ` Nick Piggin
2004-05-31 13:13 ` Tvrtko A. Uršulin
2004-05-31 13:33 ` Con Kolivas
2004-05-31 17:34 ` Andy Lutomirski [this message]
2004-05-31 10:49 ` why swap at all? jlnance
2004-06-01 11:57 ` Lenar Lõhmus
2004-06-01 12:27 ` Robin Rosenberg
2004-06-01 16:49 ` jlnance
2004-06-01 17:38 ` why swap at all? (what the user feels) Martin Olsson
2004-06-01 17:57 ` Valdis.Kletnieks
2004-06-01 18:01 ` David Schwartz
2004-06-01 19:01 ` Robin Rosenberg
2004-06-01 19:04 ` David Schwartz
2004-06-02 18:38 ` why swap at all? John Hendrikx
2004-06-01 12:21 ` David B. Stevens
2004-05-31 15:48 MM patches (was Re: why swap at all?) Zoltan Boszormenyi
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=40BB6CA8.9070307@myrealbox.com \
--to=luto@myrealbox.com \
--cc=ecki-news2004-05@lina.inka.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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