From: Lee Revell <rlrevell@joe-job.com>
To: A list for linux audio users <linux-audio-user@music.columbia.edu>
Subject: Re: [linux-audio-user] Re: linux-audio-user Digest, Vol 10, Issue 55
Date: Wed, 14 Jul 2004 13:47:18 -0400 [thread overview]
Message-ID: <1089827237.2104.53.camel@mindpipe> (raw)
In-Reply-To: <40F5582A.3020509@controlnet.com>
On Wed, 2004-07-14 at 11:58, Mark Knecht wrote:
> Markus Schwarzenberg wrote:
> > On Tue, 13 Jul 2004 10:44:44 -0700 (PDT) Brian Redfern
> > <bredfern@calarts.edu> wrote:
> >
> >
> >>2.6 on suse is also different than 2.6 fedora, because suse has a
> >>couple of audio programmers who work to make sure their kernel works
> >>with audio, so I can use all my audio apps out of the box with 9.2,
> >>and the 2.6 kernel, without latency problems, and without needing a
> >>kernel recompile.
> >
> >
> > Suse 9.2 ? I thought they are at 9.1, currently - no hints to 9.2 on
> > their web site (It's funny, there are some more "suse 9.2" google matches).
> >
> > So, apparently suse 9.1 does have an audio friendly kernel?
> >
>
> I believe that Takashi-san works for Suse. He recently posted a paper
> showing some latency numbers for different distributions. Suse did quite
> well as I remember. It was my impression that this was not an accident
> and that he had played a part in making sure this was true.
>
> It made me briefly consider trying Suse out... ;-0
>
Speaking of which, can someone from SuSe somment on whether they use a
modified ReiserFS? The tests I have been running (see my recent posts
to linux-kernel) showed some latency problems with reiserfs that I did
not see with ext3. There was a latency-related thread on LKML in March
where Takashi mentioned a few changes to reiserfs that would give
excellent latency.
It seems very likely that with these changes, reiserfs is just as good
as ext3. I have not heard much from the reiserfs advocates on this
issue.
Lee
parent reply other threads:[~2004-07-14 17:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <40F5582A.3020509@controlnet.com>]
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=1089827237.2104.53.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-audio-user@music.columbia.edu \
/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