From: u81ib6r2@umail.furryterror.org (Zygo Blaxell)
To: linux-sound@vger.kernel.org
Subject: Re: successive mmap()s will not work to record sound?
Date: Thu, 11 Feb 1999 16:39:09 +0000 [thread overview]
Message-ID: <marc-linux-sound-91875132405939@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91871041516692@msgid-missing>
In article <Pine.OSF.3.96.990210195646.13922A-100000@aurora.alaska.edu>,
Britton <fsblk@aurora.alaska.edu> wrote:
>I have been trying to write a brec-like program that will record long
>tracks of raw sound using many successive mmap()s of the same file, but it
>isn't working. I get stuff like this:
>
>incorrect number of bytes written: Interrupted system call
>Sound: Recording overrun
><DMA somethingorother times> out - IRQ/DRQ config error?
>
>ad nauseum
>
>Does this mean that my code is not keeping up with the sound card?
>
>Is this approach not feasible? Here are the salient features of the
>program:
No, it's not feasible.
The filesystem will block at inconvenient times sometimes for up to fives
seconds (this on 33MB/s UDMA AT drives). This only gets worse if you are
doing mmap().
What you want to do is read into shared memory with one process or
thread and write to disk with another process or thread. Depending on
your performance requirements even just two processes with select() is
enough.
--
Zygo Blaxell, Linux Engineer, Corel Corporation, zygob@corel.ca (work),
zblaxell@furryterror.org (play). It's my opinion, I tell you! Mine! All MINE!
Size of 'diff -Nurw [...] winehq corel' as of Thu Feb 11 11:14:01 EST 1999
Lines/files: In 489 / 13, Out 6321 / 74, Both 6807 / 86
next prev parent reply other threads:[~1999-02-11 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-11 5:18 successive mmap()s will not work to record sound? Britton
1999-02-11 16:39 ` Zygo Blaxell [this message]
1999-02-11 18:37 ` Zygo Blaxell
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-91875132405939@msgid-missing \
--to=u81ib6r2@umail.furryterror.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox