public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: A list for linux audio users <linux-audio-user@music.columbia.edu>
Cc: linux-audio-dev@music.columbia.edu,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-audio-user] 2.6.8-rc1-mm1 [and alsa xrun debugging]
Date: Fri, 16 Jul 2004 16:16:03 -0400	[thread overview]
Message-ID: <1090008963.27995.19.camel@mindpipe> (raw)
In-Reply-To: <20040716162510.7bac6a7c@mango.fruits.de>

On Fri, 2004-07-16 at 10:25, Florian Schmidt wrote:
> after reading lee's email i had to try this kernel.. so i went over to www.de.kernel.org, grabbed 2.6.8-rc1 and patched it up with this patch: 
> 
> http://www.ussg.iu.edu/hypermail/linux/kernel/0407.1/1453.html
> 
> On first sight it looks very good. many of the sporadic xruns i experienced 
> with jack in RT mode are gone. even a "find /" parallel to a "make bzImage" 
> seems not to provoke any xruns [i use ext3]. But: i use fluxbox and it supports 
> desktop wheeling [switching desktop via scrollwheel - very handy] and doing this 
> excessively and rapidly provokes xruns easily. Also starting mozilla just provoked 
> an xrun..

Try the included patch.  Andrew Morton suggested this, and it works
great for me, but it is not in -mm1.

Lee

--- drivers/char/tty_io.c_orig  2004-07-16 16:10:11.000000000 -0400
+++ drivers/char/tty_io.c       2004-07-16 16:10:31.000000000 -0400
@@ -679,17 +679,13 @@
                return -ERESTARTSYS;
        }
        if ( test_bit(TTY_NO_WRITE_SPLIT, &tty->flags) ) {
-               lock_kernel();
                written = write(tty, file, buf, count);
-               unlock_kernel();
        } else {
                for (;;) {
                        unsigned long size = max((unsigned long)PAGE_SIZE*2, 16384UL);
                        if (size > count)
                                size = count;
-                       lock_kernel();
                        ret = write(tty, file, buf, size);
-                       unlock_kernel();
                        if (ret <= 0)
                                break;
                        written += ret;



       reply	other threads:[~2004-07-16 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040716162510.7bac6a7c@mango.fruits.de>
2004-07-16 20:16 ` Lee Revell [this message]
     [not found] ` <200407161654.28004.eseol@tiscali.co.uk>
     [not found]   ` <20040716185123.2e3899bf@mango.fruits.de>
2004-07-16 20:26     ` [linux-audio-user] 2.6.8-rc1-mm1 [and alsa xrun debugging] Lee Revell

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=1090008963.27995.19.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-audio-dev@music.columbia.edu \
    --cc=linux-audio-user@music.columbia.edu \
    --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