All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>, Jan Knutar <jk-lkml@sci.fi>,
	linux-kernel@vger.kernel.org, Hans-Peter Jansen <hpj@urpla.net>,
	David Newall <davidn@davidnewall.com>,
	Theodore Tso <tytso@mit.edu>, "Fred ." <eldmannen@gmail.com>
Subject: Re: Keys get stuck
Date: Thu, 13 Mar 2008 09:19:01 -0300	[thread overview]
Message-ID: <20080313121900.GA4095@localhost.ift.unesp.br> (raw)
In-Reply-To: <Pine.LNX.4.64.0803131305540.30831@jikos.suse.cz>

On Thu 13.Mar'08 at 13:06:53 +0100, Jiri Kosina wrote:
> On Thu, 13 Mar 2008, Carlos R. Mafra wrote:
> 
> > So I would like to ask if swap letting X (and everything else in my 
> > experience) out of the cpu for extended periods is considered normal 
> > behaviour, in the sense that nobody is trying to "fix" it (due to it 
> > being considered impossible to fix)...? Sorry for being off-topic, but I 
> > run a minimal Window Maker desktop in a P4 3.0 GHz with 512 MB of RAM 
> > (around 140 MB being used as per 'free'), and trying to load a 380 MB 
> > text file in xjed editor makes my whole desktop quite unfair... it takes 
> > tens of seconds to switch desktop, type things in the terminal etc. When 
> > xjed finishes loading the text file, everything comes back to "fair" 
> > again.
> 
> I propose you start a new thread about this with proper Subject, and CC 
> the scheduler maintainers.

Right. I am sorry!

But the thing I've learned from:

http://lkml.org/lkml/2008/2/28/249

makes me _not_ think the scheduler is guilty by itself.
Although it may appear so when first-looked upon.

Now I think that the  problem I was facing that day was
also caused by swapping, which makes everything else
wait for it to finish.

So I am sorry for going off-topic here, but I couldn't
resist asking Galbraith about it.

Or I should just start a new thread like this? :-)

Petition for Ingo writing CFSS: Completely Fair Swap Scheduler




  reply	other threads:[~2008-03-13 12:18 UTC|newest]

Thread overview: 35+ 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 [this message]
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
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
     [not found] <a6meN-2aj-39@gated-at.bofh.it>
     [not found] ` <a6wxo-1xY-1@gated-at.bofh.it>
     [not found]   ` <a6wQO-1YG-1@gated-at.bofh.it>
     [not found]     ` <a6Zgb-5Hj-55@gated-at.bofh.it>
     [not found]       ` <a7iiO-2fq-39@gated-at.bofh.it>
2008-03-14 20:20         ` Bodo Eggert

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=20080313121900.GA4095@localhost.ift.unesp.br \
    --to=crmafra2@gmail.com \
    --cc=davidn@davidnewall.com \
    --cc=efault@gmx.de \
    --cc=eldmannen@gmail.com \
    --cc=hpj@urpla.net \
    --cc=jk-lkml@sci.fi \
    --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 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.