linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jogi@planetzork.ping.de
To: "Andrea Arcangeli" <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.10-pre11: alsaplayer skiping during kernel build (-pre10 did not)
Date: 18 Sep 2001 17:14:16 +0200	[thread overview]
Message-ID: <20010918171416.A6540@planetzork.spacenet> (raw)

Hello Andrea,

I gave your new vm a try and I have to report a problem. System is an
Athlon 1200 with 256MB memory. Workload:

1. top refreshing every second reniced to -10
2. alsaplayer -n -q -r *.wav
3. make -j4 bzImage modules

The problem is that with 2.4.10-pre11 alsaplayer is skiping very much.
Almost every ten seconds and then the break seems to be relatevily long
(like >1s). With 2.4.10-pre10 I noticed alsaplayer skiping once or twice
during the whole build (which takes about 6min) for a very short time
(like a cd player skipping over a scratch). Here is the diff output of
time -v of the make -j4 command:

planetzork:/usr/src/linux# diff -u time.out-2.4.10-pre1*
--- time.out-2.4.10-pre10-1000823801    Tue Sep 18 16:42:30 2001
+++ time.out-2.4.10-pre11-1000824952    Tue Sep 18 17:01:39 2001
@@ -1,16 +1,16 @@
-       Command being timed: "sh -c make dep clean>logfile-2.4.10-pre10 2>&1 && make -j4 bzImage modules>>logfile-2.4.10-pre10 2>&1"
-       User time (seconds): 241.28
-       System time (seconds): 17.82
+       Command being timed: "sh -c make dep clean>logfile-2.4.10-pre11 2>&1 && make -j4 bzImage modules>>logfile-2.4.10-pre11 2>&1"
+       User time (seconds): 242.11
+       System time (seconds): 17.10
        Percent of CPU this job got: 74%
-       Elapsed (wall clock) time (h:mm:ss or m:ss): 5:49.57
+       Elapsed (wall clock) time (h:mm:ss or m:ss): 5:47.60
        Average shared text size (kbytes): 0
        Average unshared data size (kbytes): 0
        Average stack size (kbytes): 0
        Average total size (kbytes): 0
        Maximum resident set size (kbytes): 0
        Average resident set size (kbytes): 0
-       Major (requiring I/O) page faults: 901054
-       Minor (reclaiming a frame) page faults: 934971
+       Major (requiring I/O) page faults: 906843
+       Minor (reclaiming a frame) page faults: 936570
        Voluntary context switches: 0
        Involuntary context switches: 0
        Swaps: 0


Best regards,

   Jochen

-- 

Well, yeah ... I suppose there's no point in getting greedy, is there?

    << Calvin & Hobbes >>

             reply	other threads:[~2001-09-18 15:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18 15:14 jogi [this message]
2001-09-18 15:25 ` Andrea Arcangeli
2001-09-18 15:35   ` jogi
2001-09-18 15:44     ` Andrea Arcangeli
2001-09-18 15:51       ` jogi
2001-09-18 16:06       ` jogi
2001-09-18 19:28       ` Stephan von Krawczynski
2001-09-18 19:41         ` Andrea Arcangeli
2001-09-18 20:02           ` Andrew Morton
2001-09-18 20:18             ` Andrea Arcangeli
2001-09-19 12:37             ` Hugh Dickins
2001-09-19 13:21       ` jogi
2001-09-19 14:38       ` jogi
2001-09-18 15:25 ` jogi
2001-09-18 15:31   ` Andrea Arcangeli
2001-09-18 15:43     ` jogi

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=20010918171416.A6540@planetzork.spacenet \
    --to=jogi@planetzork.ping.de \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.4.10-pre11: alsaplayer skiping during kernel build (-pre10 did not)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).