All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Interactivity improvements
Date: Thu, 7 Aug 2003 13:48:17 -0700	[thread overview]
Message-ID: <20030807204817.GZ32488@holomorphy.com> (raw)
In-Reply-To: <20030807152418.GA509@malvern.uk.w2k.superh.com>

Patrick McLean <pmclean@cs.ubishops.ca> [2003-08-07]:
>> Another point is compilers, they tend to do a lot of disk I/O then 
>> become major CPU hogs, could we have some sort or heuristic that reduces 
>> the bonuses for sleeping on block I/O rather than other kinds of I/O 
>> (say pipes and network I/O in the case of X).

On Thu, Aug 07, 2003 at 04:24:18PM +0100, Richard Curnow wrote:
> What about compilers chewing on source files coming in over NFS rather
> than resident on local block devices?  The network waits need to be
> broken out into NFS versus other, or UDP versus TCP or something.  e.g.
> waits due to the user not having typed anything yet, or moved the mouse,
> are going to be on TCP connections.

I'd be interested in whatever you come up with for this, as I use NFSS
a lot.


-- wli

  parent reply	other threads:[~2003-08-07 20:47 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 [this message]
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
  -- 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=20030807204817.GZ32488@holomorphy.com \
    --to=wli@holomorphy.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 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.