Message-ID: <3F327382.5000200@cs.ubishops.ca>
Date: Thu, 07 Aug 2003 11:42:58 -0400
From: Patrick McLean <pmclean@cs.ubishops.ca>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030731
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Re: Interactivity improvements
References: <3F3261A2.9000405@cs.ubishops.ca> <20030807152418.GA509@malvern.uk.w2k.superh.com>
In-Reply-To: <20030807152418.GA509@malvern.uk.w2k.superh.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1124
Lines: 26


Richard Curnow wrote:
> * 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).
> 
> 
> 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.
> 
Maybe if we had it reduce sleeping bonuses if it's waiting on filesystem 
access, this would cover NFS as the kernel does consider it a 
filesystem, this would cover SMB, AFS, etc as well.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/