From: Xavier Bestel <xavier.bestel@free.fr>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.9-ac15 sluggish
Date: 27 Sep 2001 22:43:15 +0200 [thread overview]
Message-ID: <1001623396.18174.14.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.33L.0109271212100.19147-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109271212100.19147-100000@imladris.rielhome.conectiva>
le jeu 27-09-2001 at 17:13 Rik van Riel a écrit :
> We discovered a merge bug, -ac15 has a few lines in
> try_to_swap_out() 10 lines higher than they were in
> the patch I sent to Alan ;)
>
> This is fixed in the age+launder patch from my home
> page ard in the vmscan.c I sent to Alan for -ac16.
Mmmh ... i'm now compiling (make -j5) -ac16 under -ac15-age+launder and
it's sluggish: xmms drops audio sometimes, my mouse pointer is jerky.
Xav
next prev parent reply other threads:[~2001-09-27 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 14:46 2.4.9-ac15 sluggish Xavier Bestel
2001-09-27 15:09 ` Roberto Orenstein
2001-09-27 15:13 ` Rik van Riel
2001-09-27 20:43 ` Xavier Bestel [this message]
2001-09-27 17:27 ` 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=1001623396.18174.14.camel@nomade \
--to=xavier.bestel@free.fr \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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