From: Andrea Arcangeli <andrea@suse.de>
To: dak@gnu.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Scheduling problem with 2.4?
Date: Sat, 17 May 2003 19:41:00 +0200 [thread overview]
Message-ID: <20030517174100.GT1429@dualathlon.random> (raw)
In-Reply-To: <x54r3tddhs.fsf@lola.goethe.zz>
On Sat, May 17, 2003 at 01:22:23PM +0200, David Kastrup wrote:
>
> I have a problem with Emacs which crawls when used as a shell. If I
> call M-x shell RET and then do something like
> hexdump -v /dev/null|dd count=100k bs=1
this certainly can't be it
andrea@dualathlon:~> hexdump -v /dev/null|dd count=100k bs=1
0+0 records in
0+0 records out
andrea@dualathlon:~>
how can that run slow, there's nothing to hexdump in /dev/null and
nothing to read for dd?
One related hint, since you're playing with >4k buffers with dd, make
sure to run a -aa kernel with the lowlatency fixes (latest is
2.4.21rc2aa1), or those large writes can loop in the kernel forbid
preemption (in this case maybe not if they block in a socket/pipe before
100k is all written)
overall often people notices improvement with preempt becuse they
compare it with buggy kernels (I know this has nothing to do with your
report, but it's related to the above)
Andrea
next prev parent reply other threads:[~2003-05-17 17:28 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 [this message]
2003-05-17 19:36 ` David Kastrup
2003-05-17 20:30 ` Andrea Arcangeli
2003-05-17 20:44 ` David Kastrup
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=20030517174100.GT1429@dualathlon.random \
--to=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