public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jussi Laako <jussi.laako@kolumbus.fi>
To: mingo@elte.hu
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] improving O(1)-J9 in heavily threaded situations
Date: Sun, 10 Feb 2002 17:00:52 +0200	[thread overview]
Message-ID: <3C668B24.1A22F53@kolumbus.fi> (raw)
In-Reply-To: <Pine.LNX.4.33.0202072326410.4773-100000@localhost.localdomain>

Ingo Molnar wrote:
> 
> there is one more thing in the -K2 patch that could cause your problems.
> In kernel/softirq.c, you'll find this line:
> //__initcall(spawn_ksoftirqd);
> please uncomment it - this was just a debugging thing that was left in 
> the patch accidentally. I've made a -K3 patch that has this fixed. Do you
> still see the audio problems?

I did this and also tried -K3. It didn't fix the problem.

I addded lost block count printing to the SCHED_FIFO server processes. Most
of the loss (about 75%) happens at lowest level soundcard server and rest in
distributor process. Usually it looses 1 block at time but occasionally
there is peak of about 18 lost blocks.

If I make the client process read larger blocks (> 4kB) from the distributor
process number of lost blocks at soundcard server raises significantly. I
can make it a bit smaller without increased loss, but of course it means
larger overhead and eventually more lost blocks if made something like 512
bytes. 4 kB is optimal block size as it's also internal block size used by
soundcard and distributor servers.

4 kB block size means 2.9 ms in time in this case.


 - Jussi Laako

-- 
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B  39DD A4DE 63EB C216 1E4B
Available at PGP keyservers


  reply	other threads:[~2002-02-10 15:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-02 15:50 [PATCH] improving O(1)-J9 in heavily threaded situations Ed Tomlinson
2002-02-03 11:32 ` Ingo Molnar
2002-02-03 15:46   ` Ed Tomlinson
2002-02-04  0:46     ` Ingo Molnar
2002-02-04 19:52       ` Jussi Laako
2002-02-05  0:59         ` Ingo Molnar
2002-02-04 23:36           ` Jussi Laako
2002-02-05  1:37             ` Ingo Molnar
2002-02-06  0:43               ` Jussi Laako
2002-02-06 12:37                 ` Ingo Molnar
2002-02-07  1:10                   ` Jussi Laako
2002-02-07 22:28                 ` Ingo Molnar
2002-02-10 15:00                   ` Jussi Laako [this message]
2002-02-05  1:41             ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2002-02-03  6:00 Ed Tomlinson
     [not found] <Pine.LNX.4.33.0202040627001.22583-100000@localhost.localdomain>
2002-02-04  4:40 ` Ed Tomlinson
2002-02-04 12:30   ` Ingo Molnar
2002-02-04 12:36   ` Ingo Molnar
2002-02-04 10:47     ` Arjan van de Ven
2002-02-04 14:09       ` Ingo Molnar
2002-02-04 12:18     ` Ed Tomlinson
2002-02-04 20:01   ` Jussi Laako
2002-02-04 22:06     ` Ingo Molnar
2002-02-04 22:56       ` Jussi Laako
2002-02-05  0:56         ` Ingo Molnar
2002-02-04 23:32           ` Jussi Laako
2002-02-05  1:34             ` Ingo Molnar
2002-02-04 22:24   ` Bill Davidsen
2002-02-04 12:32 Ed Tomlinson
2002-02-04 12:33 ` Arjan van de Ven

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=3C668B24.1A22F53@kolumbus.fi \
    --to=jussi.laako@kolumbus.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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