Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 7 Aug 2003 11:33:22 -0700 | From | Mike Fedyk <> | Subject | Re: Interactivity improvements |
| |
On Thu, Aug 07, 2003 at 11:42:58AM -0400, Patrick McLean wrote: > > > 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
We are already doing this.
> access, this would cover NFS as the kernel does consider it a > filesystem, this would cover SMB, AFS, etc as well.
Network interactivity is dealing with sockets, and such. Accessing NFS (and other network filesystems) deals with a virtual block device, and gives similar patterns to a local block device. - 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/
| ![\](/images/icornerr.gif) |