All of lore.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Mikhail Ramendik <mr@ramendik.ru>
Cc: ck@vds.kolivas.org, Rik van Riel <riel@conectiva.com.br>,
	Andrew Morton <akpm@osdl.org>,
	linux <linux-kernel@vger.kernel.org>
Subject: Re: [ck] 2.6.7 backport request, spinoff idea
Date: Sun, 19 Dec 2004 11:42:31 +1100	[thread overview]
Message-ID: <41C4CE77.40601@kolivas.org> (raw)
In-Reply-To: <200412190321.16567.mr@ramendik.ru>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

Mikhail Ramendik wrote:
> Con Kolivas wrote:
> 
> 
>>Actually I wonder if the swap token is responsible in 2.6.10-rc3
>>
>>Try this
>>echo 0 > /proc/sys/vm/swap_token_timeout
> 
> 
> Well, this makes things really better, although not as good as 2.6.8.1. There 
> are kswapd cpu jumps and screen freezes, but they only last several seconds 
> (the longest is in the very beginning, about 15-20 sec).
> 
> Thanks! This makes the system much more useable.

This is worth posting to lkml so I've cc'ed a few relevant people (there 
is already a thread about this there). Rik care to comment? I recall 
pointing out this test case a while back. Got any way to make it harder 
to trigger the swap token? It seems to affect normal workloads adversely 
considering how rare swap thrashing actually occurs.

Con

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

       reply	other threads:[~2004-12-19  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200412171504.41234.mr@ramendik.ru>
     [not found] ` <41C4A670.9090009@kolivas.org>
     [not found]   ` <41C4A899.10102@kolivas.org>
     [not found]     ` <200412190321.16567.mr@ramendik.ru>
2004-12-19  0:42       ` Con Kolivas [this message]
2004-12-19  1:29         ` [ck] 2.6.7 backport request, spinoff idea Con Kolivas
2004-12-19  4:26           ` Rik van Riel

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=41C4CE77.40601@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=akpm@osdl.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mr@ramendik.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.