public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David.Kastrup@t-online.de (David Kastrup)
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling problem with 2.4?
Date: 17 May 2003 22:44:16 +0200	[thread overview]
Message-ID: <x565o9717j.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20030517203045.GZ1429@dualathlon.random>

Andrea Arcangeli <andrea@suse.de> writes:

> > The interactive session tends to be somewhat worse, but the command
> > line version is bad enough for a demonstration.
> 
> this is within emacs:
> 
>    1 blocks with size   95
>    1 blocks with size  146
>    1 blocks with size  175

[...]

>    1 blocks with size  980
>    2 blocks with size  987
>    1 blocks with size  991
>    1 blocks with size  998
>    1 blocks with size 1023
>    8 blocks with size 1024
> 
> from the shell prompt:
> 

[...]

Wel, those are excellent results and as it should be.

> my emacs is:
> 
> GNU Emacs 21.2.1

Same here.

I am talking about the kernel coming with RedHat 9, uname -a gives
Linux lola.goethe.zz 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux

Unfortunately, this kernel is here to stay for quite a while, and I
would want to find a way to let Emacs cooperate with it better without
telling people to recompile the kernel or wait a year.

> > Again, I am pretty sure that Emacs is at fault too, but I don't
> > understand the implications of what scheduling behavior causes the
> > pipes to remain mostly empty, with an occasional full filling.  It
> > would be better if Emacs would not be context-switched into the
> > moment something appears in the pipe, but if the writer to the
> > pipe would keep the opportunity to fill'er'up until it is either
> > preempted or needs to wait.  If there was some possibility to
> > force this behavior from within Emacs, this would be good to know.
> 
> I don't see any slowdown here.

Which kernel?  Oh, and of course: on a SMP machine the problem would
not be visible since then the context switch to Emacs does not stop
the other process from stuffing into the pipe.

> 	http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/kernels/v2.4/2.4.21rc2aa1/9998_lowlatency-fixes-12

Taking notice, but will need some time to apply.  And I really would
want to find a way to avoid triggering this problem.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-05-17 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 11:22 Scheduling problem with 2.4? David Kastrup
2003-05-17 17:41 ` Andrea Arcangeli
2003-05-17 19:36   ` David Kastrup
2003-05-17 20:30     ` Andrea Arcangeli
2003-05-17 20:44       ` David Kastrup [this message]
2003-05-17 21:53         ` Andrea Arcangeli
2003-05-17 22:37           ` David Kastrup
2003-05-17 23:50             ` Andrea Arcangeli
2003-05-18  0:16               ` David Schwartz
2003-05-18  1:06                 ` Andrea Arcangeli
2003-05-18  9:41                   ` David Kastrup
2003-05-18  8:55                 ` Mike Galbraith
2003-05-18 17:46                   ` David Schwartz
2003-05-18 23:18                     ` Andrea Arcangeli
2003-05-19  2:59                       ` David Schwartz
2003-05-18 23:11                   ` Andrea Arcangeli
2003-05-19  7:16                     ` Mike Galbraith
2003-05-19  4:02                   ` Mike Galbraith
2003-05-18  0:24               ` David Kastrup
2003-05-17 21:54         ` Barry K. Nathan

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=x565o9717j.fsf@lola.goethe.zz \
    --to=david.kastrup@t-online.de \
    --cc=andrea@suse.de \
    --cc=dak@gnu.org \
    --cc=linux-kernel@vger.kernel.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