All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Patrick McLean <pmclean@cs.ubishops.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interactivity improvements
Date: Thu, 07 Aug 2003 10:41:18 -0700	[thread overview]
Message-ID: <1060278078.15243.71.camel@localhost> (raw)
In-Reply-To: <3F3261A2.9000405@cs.ubishops.ca>

On Thu, 2003-08-07 at 07:26, Patrick McLean wrote:

> Finally, the interactivity estimator seems to be quite a bit of code, 
> which certain people have no real useful (in servers for example) and I 
> would imagine that it does reduce throughput

Actually, it should improve I/O throughput. What it might hurt is
computational performance, but only at the expense of benefiting other
processes.

The reason it benefits throughput is that file I/O is definitely marked
interactive, and that results in file I/O being able to quickly wake up,
dispatch the I/O, and go back to sleep. Its the usual treatment given to
I/O, and it works.

	Robert Love



  parent reply	other threads:[~2003-08-07 17:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 14:26 Interactivity improvements Patrick McLean
2003-08-07 15:24 ` Richard Curnow
2003-08-07 15:42   ` Patrick McLean
2003-08-07 18:33     ` Mike Fedyk
2003-08-07 20:48   ` William Lee Irwin III
2003-08-07 21:26     ` Bernd Eckenfels
2003-08-07 23:05       ` Timothy Miller
2003-08-07 15:31 ` Felipe Alfaro Solana
2003-08-07 17:41 ` Robert Love [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-04 16:07 [PATCH] O13int for interactivity Con Kolivas
2003-08-05  2:20 ` Con Kolivas
2003-08-05  2:21   ` Nick Piggin
2003-08-05  3:06     ` Con Kolivas
2003-08-05  3:17       ` Nick Piggin
2003-08-06 18:48         ` Interactivity improvements Timothy Miller
2003-08-06 19:01           ` Mike Fedyk
2003-08-06 20:09           ` Helge Hafting
2003-08-06 21:15           ` Con Kolivas

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=1060278078.15243.71.camel@localhost \
    --to=rml@tech9.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmclean@cs.ubishops.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.