From: Anthony DiSante <orders@nodivisions.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Audio skips when RAM is ~full
Date: Sat, 01 Nov 2003 07:48:25 -0500 [thread overview]
Message-ID: <3FA3AB99.1060408@nodivisions.com> (raw)
In-Reply-To: <20031101071907.GA6300@alpha.home.local>
Willy Tarreau wrote:
>>Actually, I don't scan the disk to find random albums; I have a text file
>>that contains a list of every album's full path, and I pick a random line
>>from that file. So only the selected album's directory gets scanned. And
>>the mp3 partition is mounted read-only (I should have mentioned that
>>before), so the atimes shouldn't be getting written as it is.
>
>
> OK, so it's not a disk IO problem at all. It's really related to the sound
> driver it seems. Now that you say it, I remember having noticed skips on
> my laptop with a via 82cxxx chip after tens of minutes playing. At first
> I thought it was related to other activity on the system, but it did exactly
> what you describe, play seconds 1, 2, then 5 without a hole between them.
> There may be a problem with the way the audio buffer gets allocated or freed.
Yeah... in my experience, the whole ac'97 deal is pretty buggy (for one
thing, with both ALSA and OSS drivers, output is distorted unless I keep the
volume below ~70%...). But as I said, the skipping only happens when the
memory is full, or getting close to full. If I select specific albums to
play instead of using my random function, I can usually play a few albums
and there aren't any skips, not until the memory gets pretty full.
>>So I'm guessing that there isn't actually a way to manually move
>>buffer-data out of RAM?
>
>
> Yes, there is. I have a quick'n'dirty program which does exactly that.
> Basically, you tell it how many kB you want to free, then it allocates
> and uses that amount of memory, frees it and exits. Buffered data gets
> flushed very quickly. I sometimes give it a try before starting to work
> on large kernel trees, because it helps the entire directories to fit in
> cache.
>
> Here it is if you're interested. Don't start it without an argument, it
> will try to allocate 4G !
4G!! (Note to self: s/ffffffff/0000ffff/...) Thanks a lot, I'll give this a
try. It certainly works here on my home system.
-Anthony
http://nodivisions.com/
next prev parent reply other threads:[~2003-11-01 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 5:31 Audio skips when RAM is ~full Anthony DiSante
2003-11-01 6:20 ` Willy Tarreau
2003-11-01 6:34 ` Anthony DiSante
2003-11-01 7:19 ` Willy Tarreau
2003-11-01 12:48 ` Anthony DiSante [this message]
2003-11-01 14:57 ` Jaroslav Kysela
2003-11-01 9:43 ` Maciej Zenczykowski
2003-11-01 18:08 ` Pavel Machek
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=3FA3AB99.1060408@nodivisions.com \
--to=orders@nodivisions.com \
--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