From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-ac16
Date: Mon, 20 Dec 2004 14:48:46 +0000 [thread overview]
Message-ID: <1103554123.30268.19.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0412181606050.21338@yvahk01.tjqt.qr>
On Sad, 2004-12-18 at 15:06, Jan Engelhardt wrote:
> >> Andrea's fix and the selection changes should go into 2.6.10, but I
> >> suspect that the VM gurus havent still reached a point, where they
> >> agree. I also have the feeling that the problem is partially ignored.
> >> Obviously has everybody plenty of memory in his boxes. </rant off>
>
> Well you can always take out your VMware and cut it down to <few RAM> MB by
> hand, just to get an experience how "low-end" users feel.
Or boot with mem=. I actually do test runs with -ac on a 128Mb box with
about 16Mb of that stolen as video ram. 2.6.9 isn't behaving perfectly
but seems reasonably ok for most loads except brokenoffice
next prev parent reply other threads:[~2004-12-20 15:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 18:43 Linux 2.6.9-ac16 Alan Cox
2004-12-17 11:23 ` Arjan van de Ven
2004-12-17 18:54 ` Francois Romieu
2004-12-17 13:08 ` Chris Ross
2004-12-17 14:51 ` Chris Friesen
2004-12-17 15:45 ` Chris Ross
2004-12-18 6:01 ` Thomas Gleixner
2004-12-18 15:11 ` Bill Davidsen
2004-12-18 15:06 ` Jan Engelhardt
2004-12-18 16:01 ` Chris Ross
2004-12-20 14:48 ` Alan Cox [this message]
2004-12-20 16:19 ` Chris Ross
2004-12-20 19:54 ` Alan Cox
2004-12-19 16:22 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 23:35 Chuck Ebbert
2004-12-20 17:27 ` Chris Friesen
2004-12-21 9:11 Chuck Ebbert
2004-12-21 23:49 Chuck Ebbert
2004-12-21 23:58 ` Nick Piggin
2004-12-22 2:49 ` Con Kolivas
2004-12-22 6:44 Chuck Ebbert
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=1103554123.30268.19.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox