linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Zenczykowski <maze@cela.pl>
To: Anthony DiSante <orders@nodivisions.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Audio skips when RAM is ~full
Date: Sat, 1 Nov 2003 10:43:42 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0311011042440.23028-100000@gaia.cela.pl> (raw)
In-Reply-To: <3FA353E4.60906@nodivisions.com>

> So I'm guessing that there isn't actually a way to manually move buffer-data 
> out of RAM?

Just the naive allocate X MB, set the first byte of every 4KB (PageSize) 
block to 1 and then free the memory - presto X MB free RAM.

Cheers,
MaZe.



  parent reply	other threads:[~2003-11-01  9:43 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
2003-11-01 14:57         ` Jaroslav Kysela
2003-11-01  9:43     ` Maciej Zenczykowski [this message]
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=Pine.LNX.4.44.0311011042440.23028-100000@gaia.cela.pl \
    --to=maze@cela.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orders@nodivisions.com \
    /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;
as well as URLs for NNTP newsgroup(s).