From: Jan Knutar <jk-lkml@sci.fi>
To: linux-kernel@vger.kernel.org
Cc: Helge Hafting <helgehaf@mail.aitel.hist.no>,
Helge Hafting <helge.hafting@aitel.hist.no>,
Mike Galbraith <efault@gmx.de>, Hans-Peter Jansen <hpj@urpla.net>,
Jiri Kosina <jkosina@suse.cz>,
David Newall <davidn@davidnewall.com>,
Theodore Tso <tytso@mit.edu>, "Fred ." <eldmannen@gmail.com>
Subject: Re: Swap makes X unfair (was Re: Keys get stuck)
Date: Sun, 16 Mar 2008 17:27:01 +0200 [thread overview]
Message-ID: <200803161727.02059.jk-lkml@sci.fi> (raw)
In-Reply-To: <47DA5B36.9060209@mail.aitel.hist.no>
On Friday 14 March 2008 13:02, Helge Hafting wrote:
> Normally, memory that is used all the time does not get
> swapped out. If you use X while the machine is swapping,
> you will normally see lots of little delays, not
> one longe freeze. So this may have been something else.
When it happens to me, the pointer usually updates only about 1 - 2
times per second, which seems to be enough to cause keyboard repeat
problems as well.
If the swapfile usage is 0 when a big swapout takes place, I usually see
about 6M/sec pushed to disc and rarely pointer or keyboard anomalies.
After running a few more days though, swapping rates drop to 1.3M per
sec or worse. The delays in X get bigger too, sometimes several seconds
long. I guess if the kernel swaps out a piece of X that X needs, then
it takes much much longer to get it back at that low swap rate, and it
ends up manifesting itself as pointer jitter and keyboard repeat
problems.
The pointer stutter can be considered acceptable, I guess, atleast there
the pointer (eventually) jumps to where I expect it to go based on how
much I move the mouse...
I have to wonder what X is doing to break the keyboard...
next prev parent reply other threads:[~2008-03-16 15:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 23:32 Keys get stuck Fred .
2008-03-12 0:04 ` Andrew Morton
2008-03-12 8:48 ` Sebastien Dugue
2008-03-12 10:32 ` Jiri Kosina
2008-03-12 10:44 ` David Newall
2008-03-12 14:47 ` Theodore Tso
2008-03-12 15:20 ` Stephen Hemminger
2008-03-12 16:47 ` David Newall
2008-03-12 16:49 ` Jiri Kosina
2008-03-12 21:22 ` Hans-Peter Jansen
2008-03-13 5:42 ` Mike Galbraith
2008-03-13 9:48 ` Jan Knutar
2008-03-13 11:28 ` Mike Galbraith
2008-03-13 11:31 ` Jiri Kosina
2008-03-13 12:02 ` Mike Galbraith
2008-03-13 12:02 ` Carlos R. Mafra
2008-03-13 12:06 ` Jiri Kosina
2008-03-13 12:19 ` Carlos R. Mafra
2008-03-13 12:21 ` Mike Galbraith
2008-03-13 14:18 ` Helge Hafting
2008-03-13 15:13 ` Swap makes X unfair (was Re: Keys get stuck) Carlos R. Mafra
2008-03-14 11:02 ` Helge Hafting
2008-03-15 22:11 ` Carlos R. Mafra
2008-03-16 15:27 ` Jan Knutar [this message]
2008-03-14 18:34 ` Keys get stuck Pavel Machek
2008-03-13 17:14 ` Pavel Machek
2008-03-13 17:56 ` Fred .
2008-03-13 18:03 ` Pavel Machek
2008-03-14 9:21 ` Jiri Kosina
2008-03-14 18:24 ` Pavel Machek
2008-03-14 21:34 ` Lennart Sorensen
2008-03-14 13:30 ` Lennart Sorensen
2008-03-14 19:35 ` Pavel Machek
2008-03-13 13:01 ` Mark Lord
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=200803161727.02059.jk-lkml@sci.fi \
--to=jk-lkml@sci.fi \
--cc=davidn@davidnewall.com \
--cc=efault@gmx.de \
--cc=eldmannen@gmail.com \
--cc=helge.hafting@aitel.hist.no \
--cc=helgehaf@mail.aitel.hist.no \
--cc=hpj@urpla.net \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®