Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: linux-sound@vger.kernel.org
Subject: Re: [alsa-devel] New scheduling latencies during audio playing +
Date: Thu, 17 Jun 1999 19:35:13 +0000	[thread overview]
Message-ID: <marc-linux-sound-92964890718034@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92962100616666@msgid-missing>

On Thu, 17 Jun 1999, Juhana Sadeharju wrote:

>How about defining a maximum number of swap pages to write to disk at
>a time? Does kernel really have to wait for the disk operation to complete?

We just have such limit for the swap and it's set to 32 pages if I remeber
well. In the normal write to disk (via filesystem) case instead the limit
is forced to the 42 requests slot shared by all block-writes operations.
That make sense but it become an overkill for reads if we are writing
continously to disk.

Andrea Arcangeli

      reply	other threads:[~1999-06-17 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-17 12:02 [alsa-devel] New scheduling latencies during audio playing + heavy disk I/O on various kernels Juhana Sadeharju
1999-06-17 19:35 ` Andrea Arcangeli [this message]

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-92964890718034@msgid-missing \
    --to=andrea@suse.de \
    --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