All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-sound@vger.kernel.org
Subject: Re: Bad MIDI performance : 10ms latency instead of the expected
Date: Thu, 26 Aug 1999 20:41:56 +0000	[thread overview]
Message-ID: <marc-linux-sound-93570642713729@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-93568883025986@msgid-missing>

> > 		if(current->need_resched())
> > 			schedule();
> > 	}
> Do you think there are some benefits by inserting the re-schedule in the
> drivers/sound/mpu401.c file ? ( less CPU usage)
> 
> for (timeout = 30000; timeout > 0 && !output_ready(devc); timeout--);
> 
> But since the FIFO is only 2 bytes long = 600usecs, 
> the schedule() could cause a MIDI bandwidth decrease,
> but would keep CPU load down , right ?
> Why was the MPU401 code not tuned that way ?

Hannu tuned MPU401, Im not precisely sure how he tuned it, but it should
be sufficiently short the need_resched check isnt needed

  parent reply	other threads:[~1999-08-26 20:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-26 17:34 Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 18:42 ` Bad MIDI performance : 10ms latency instead of the expected Jaroslav Kysela
1999-08-26 19:38 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 20:20 ` Bad MIDI performance : 10ms latency instead of the expected Alan Cox
1999-08-26 20:41 ` Alan Cox [this message]
1999-08-26 20:42 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Benno Senoner
1999-08-26 20:51 ` Bad MIDI performance : 10ms latency instead of the expected Jaroslav Kysela
1999-08-26 21:04 ` Alan Cox
1999-08-26 21:53 ` Benno Senoner
1999-09-18 21:26 ` Bad MIDI performance : 10ms latency instead of the expected 1-1.5ms Peter Enderborg

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=marc-linux-sound-93570642713729@msgid-missing \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-sound@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.