Re: tracing disk accesses

To: "Gregory S. Stark" <gsstark@mit.edu>, Douglas Bates <bates@stat.wisc.edu>
Cc: debian-devel@lists.debian.org
Subject: Re: tracing disk accesses
From: Joey Hess <joey@kitenet.net>
Date: Sat, 27 Jun 1998 14:30:18 -0700
Message-id: <[🔎] 19980627143018.A1606@kitenet.net>
Mail-followup-to: "Gregory S. Stark" <gsstark@mit.edu>, Douglas Bates <bates@stat.wisc.edu>, debian-devel@lists.debian.org
In-reply-to: <[🔎] ycqwwa2hagb.fsf@mit.edu>; from Gregory S. Stark on Sat, Jun 27, 1998 at 04:11:00PM -0400
References: <[🔎] 6rd8bwc4dh.fsf@verdi.stat.wisc.edu> <[🔎] ycqwwa2hagb.fsf@mit.edu>

Gregory S. Stark wrote:
> Also, it could just be the normal asynchronous page flushing. You can try
> running the modified "laptop" bdflush that stops flushing buffers when the
> machine is idle for a while.

Where do you get that?

-- 
see shy jo


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

References:
- tracing disk accesses
  - From: Douglas Bates <bates@stat.wisc.edu>
- Re: tracing disk accesses
  - From: gsstark@mit.edu (Gregory S. Stark)

Prev by Date: Re: emacs -> emacs19. Why?
Next by Date: Re: libc6_2.0.7 release notes...
Previous by thread: Re: tracing disk accesses
Next by thread: Re: tracing disk accesses
Index(es):
- Date
- Thread