From: "szonyi calin" <caszonyi@yahoo.com>
To: azarah@nosferatu.za.org, Con Kolivas <kernel@kolivas.org>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
Willy Tarreau <willy@w.ods.org>,
Mark Hahn <hahn@physics.mcmaster.ca>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
gillb4@telusplanet.net
Subject: Re: xterm scrolling speed - scheduling weirdness in 2.6 ?!
Date: Sun, 4 Jan 2004 23:58:27 +0100 (CET) [thread overview]
Message-ID: <20040104225827.39142.qmail@web40613.mail.yahoo.com> (raw)
In-Reply-To: <1073227359.6075.284.camel@nosferatu.lan>
--- Martin Schlemmer <azarah@nosferatu.za.org> a écrit : > On
Sun, 2004-01-04 at 14:45, Con Kolivas wrote:
> > On Sun, 4 Jan 2004 22:13, Martin Schlemmer wrote:
> > > On Sun, 2004-01-04 at 10:49, Con Kolivas wrote:
> > > > > I added a fprintf(stderr, "%d\n", amount); to that
> code and indeed
> > > > > amount was *always* 1 no matter what I did (it even
> was 1 when the
> > > > > (dmesg/...) output came in fast). And jump scrolling
> would take place
> > > > > if amount > 59 in my case... can this still be not a
> schedulers issue ?
> > > > >
> > > > >
> > > > > Looking at that how can it not be a scheduling problem
> ....
> > > >
> > > > Scheduling problem, yes; of a sort.
> > > >
> > > > Solution by altering the scheduler, no.
> > > >
> > > > My guess is that turning the xterm graphic candy up or
> down will change
> > > > the balance. Trying to be both gui intensive and a
> console is where it's
> > > > happening. On some hardware you are falling on both
> sides of the fence
> > > > with 2.6 where previously you would be on one side.
> > >
> > > So its Ok for 'eye candy' to 'lag', but xmms should not
> skip? Anyhow,
> > > its xterm that he have issues with, not gnome-terminal or
> such with
> > > transparency. I smell something ...
> >
> > Sigh...
> >
> > Xmms was a simple test case long forgotten but most still
> think all I did was
> > make an xmms scheduler. Deleting one character from sched.c
> before all of my
> > patches would make the scheduler ideal for xmms. Any
> braindead idiot can tune
> > a scheduler for just one application.
>
> Well, its the favorite example 8)
>
> > An application that changes it's
> > behaviour dynamically well in the setting of a particular
> scheduler, though?
> > Should a scheduler be tuned to suit a coding style or quirk?
>
> >
>
> But the scheduler changes to a particular application? I
> still am of
> opinion that the current scheduler in mainline 'breaks'
> priorities ...
> call it dynamic tuning or whatever you like. Now something
> gets
> priority while something else starves.
>
> > I should go back to lurking before people start calling me
> names. This thread
> > has gone long enough for that. If I hadn't said anything it
> would have died
> > out by now.
>
> Well, I have stayed out of this for months now, as its always
> 'they' at
> fault - that app, or piece of code. Sure, I am one of those
> whining
> users, and I have no particular interest in the scheduler code
> - that
> is if it behaves like it should. But whatever is in now, just
> do not
> behave as expected, and call it a feature or whatever you
> want, if it
> deviates the definition, then what should we call it? Or if
> its a
> feature, can we have the weirdness in priorities disabled by
> default
> with a sysctl or sysfs switch?
>
> > Instead I'm drawing attention to my fundamentally flawed
> code.
> >
>
> The scrolling is but one part. Just starting an app, or
> running
> 'vim /etc/fstab' for example takes ages some times, even with
> minimal load. If xterm, gnome-term, aterm, multi-gnome-term,
> etc is broken, how do we fix it then? What about some of the
> other issues? If its a problem with those apps, why is it I
> still
> wonder what they are doing wrong, and it not fixed?
>
> Do not worry, _I_ will go back to lurking about this issue
> _again_,
> but after _once_again_ seeing a issue about this being blown
> off
> as being something wrong with 'it', and some facts (you did
> see
> that the skipping code for the other user _never_ kicked in)
> were just ignored, I just could not help myself - sorry.
>
> At least I will not experience those issues of the others, and
> hopefully Nick will not stop his work, or things change too
> much
> to adapt his patch.
>
how much free memory do you have when this happens ?
I had
a similar problem. It was easily reproducive doing
a du -sh / and then trying to do other things.
It didn't happend all the time but most of the time
Doing a
echo 16384 >/proc/sys/vm/min_free_kbytes
seems to help the kernel remember that it has some swap and he
*has* to use it in some cases
>
> Thanks,
>
> --
> Martin Schlemmer
>
> ATTACHMENT part 2 application/pgp-signature name=signature.asc
=====
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
_________________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com
next prev parent reply other threads:[~2004-01-04 22:58 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0401031439060.24942-100000@coffee.psychology.mcmaster.ca>
2004-01-03 20:19 ` Soeren Sonnenburg
2004-01-03 21:00 ` Con Kolivas
2004-01-03 21:10 ` Soeren Sonnenburg
2004-01-03 21:15 ` Con Kolivas
2004-01-03 23:35 ` Willy Tarreau
2004-01-04 0:11 ` Soeren Sonnenburg
2004-01-04 1:42 ` Con Kolivas
2004-01-04 3:32 ` Tim Connors
2004-01-04 5:58 ` Con Kolivas
2004-01-06 1:09 ` Peter Osterlund
2004-01-06 1:37 ` Nick Piggin
2004-01-06 2:28 ` Peter Osterlund
2004-01-06 2:50 ` Nick Piggin
2004-01-06 6:27 ` Nick Piggin
2004-01-05 22:25 ` Bryan Whitehead
2004-01-04 8:09 ` Soeren Sonnenburg
2004-01-04 8:49 ` Con Kolivas
2004-01-04 11:13 ` Martin Schlemmer
2004-01-04 11:24 ` Soeren Sonnenburg
2004-01-04 12:45 ` Con Kolivas
2004-01-04 14:42 ` Martin Schlemmer
2004-01-04 18:40 ` mikeg
2004-01-04 22:58 ` szonyi calin [this message]
2004-01-04 23:33 ` Willy Tarreau
2004-01-04 23:44 ` Valdis.Kletnieks
2004-01-04 23:47 ` Mike Fedyk
2004-01-05 8:39 ` Soeren Sonnenburg
2004-01-05 20:38 ` Martin Schlemmer
2004-01-05 9:18 ` Soeren Sonnenburg
2004-01-05 17:20 ` Martin Schlemmer
2004-01-05 17:21 ` Willy Tarreau
2004-01-05 9:50 ` Kenneth Johansson
2004-01-05 10:17 ` Soeren Sonnenburg
2004-04-02 18:22 ` solved (was Re: xterm scrolling speed - scheduling weirdness in 2.6 ?!) Soeren Sonnenburg
2004-04-03 5:35 ` Tim Connors
2004-04-03 6:06 ` Tim Connors
2004-04-03 14:11 ` Jamie Lokier
2004-01-05 8:26 ` xterm scrolling speed - scheduling weirdness in 2.6 ?! Soeren Sonnenburg
2004-01-04 8:54 ` Lincoln Dale
2004-01-04 9:17 ` Nick Piggin
2004-01-04 10:24 ` Soeren Sonnenburg
2004-01-04 11:12 ` Mike Fedyk
2004-01-04 11:17 ` Soeren Sonnenburg
2004-01-04 11:20 ` Mike Fedyk
2004-01-04 11:19 ` Willy Tarreau
2004-01-05 0:48 ` Nick Piggin
2004-01-04 11:46 ` Nicks's scheduler's OK [was Re: xterm scrolling speed - scheduling weirdness in 2.6 ?!] Willy Tarreau
2004-01-04 12:07 ` xterm scrolling speed - scheduling weirdness in 2.6 ?! Willy Tarreau
2004-01-05 0:51 ` Nick Piggin
2004-01-05 18:37 ` Willy Tarreau
2004-01-06 0:33 ` Nick Piggin
2004-01-04 10:11 ` Soeren Sonnenburg
2004-01-05 10:31 ` venom
2004-01-03 21:18 ` Willy Tarreau
2004-01-03 21:39 Bob Gill
[not found] <Pine.LNX.4.44.0401031402210.24942-100000@coffee.psychology.mcmaster.ca>
2004-01-03 19:07 ` Soeren Sonnenburg
-- strict thread matches above, loose matches on Subject: below --
2004-01-03 18:52 Soeren Sonnenburg
2004-01-03 19:19 ` Willy Tarreau
2004-01-04 20:47 ` Peter Chubb
2004-01-04 20:54 ` Willy TARREAU
2004-01-05 3:46 ` Peter Chubb
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=20040104225827.39142.qmail@web40613.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=azarah@nosferatu.za.org \
--cc=gillb4@telusplanet.net \
--cc=hahn@physics.mcmaster.ca \
--cc=kernel@kolivas.org \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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
all inboxes | Powered by JetHome®