public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Andy Campbell <andycampbell.uk@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: High latency with ext4 / jbd2 kernel thread
Date: Tue, 12 Jul 2011 07:17:44 -0400	[thread overview]
Message-ID: <A9ADAB08-144C-4636-A02B-076CF47300F4@mit.edu> (raw)
In-Reply-To: <CALEedhfHQBiCxv06X3w-JwUzP+beJ9+_zUbr=9vHErp+ew1r=w@mail.gmail.com>


On Jul 11, 2011, at 8:07 PM, Andy Campbell wrote:

> Hi ext4 mailing list members,
> 
> I hope you can help me with a problem.
> 
> I recently upgraded my main audio PC to Fedora FC15 and, at the same
> time, reformatted by root drive to ext4.  Since this upgrade this, my
> system has high system latency which is causing my audio hardware
> (firewire) to experience buffer under-runs (XRUNs).  This causes
> "unhandled xrun" errors and the audio software fails.

What were you using before?  ext3 ?   It may be that ext4's default use of
barriers (for safety reasons) is causing a difference.   Try mounting your
file systems with barrier=0.   For the root filesystem, add "rootflags=barrier=0".
This is an unsafe way to run, in that if you have a power failure while you
are writing to the disk, your file system(s) could get corrupted.   Ext3 
defaulted to this for historical reasons (although the enterprise Linux systems,
RHEL and SuSE changed the default for safety reasons).

If this solves the problem, I'd suggest that you look into finding ways to
increase the buffer size of your audio system (were you recording or
doing playback at the time).   You might also try to see if there was 
some amount of disk activity (especially write activity) that could be
avoided or find some way of avoiding the use of fsync() so that you
can re-enable write barriers without causing your latency skips.

Regards,

-- Ted



  parent reply	other threads:[~2011-07-12 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12  0:07 High latency with ext4 / jbd2 kernel thread Andy Campbell
2011-07-12 10:48 ` Tao Ma
2011-07-12 11:17 ` Theodore Tso [this message]
2011-07-15 10:00   ` Andy Campbell

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=A9ADAB08-144C-4636-A02B-076CF47300F4@mit.edu \
    --to=tytso@mit.edu \
    --cc=andycampbell.uk@gmail.com \
    --cc=linux-ext4@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