Re: A question about sync

Kevin Lentin (kevinl@cs.monash.edu.au)
Wed, 8 Apr 1998 15:58:05 +1000

On Tue, Apr 07, 1998 at 10:55:01PM -0500, Billy Harvey wrote:
> 3. If we do a disk-activity-activated-sync, as alluded to in the
> first question, would it be very difficult to cause update to wait
> until other disk activity was completed, plus some amount of slop
> time? This would prevent any unnecessary thrashing, as the amount of
> data to flush after 30 minutes of non-sync can be extensive.

An ideal situation would be for update to have two different intervals. One
interval is used when the disc is spun up - this would be a typical 5 to 30
seconds. When the disk is spun down, it would use the second interval which
you might set to 15 or 30 minutes. If some activity caused a spin-up then
the shorter interval takes hold and a flush would probably occur.

I'm sure update could be modified to use the same calls as hdparm to
discover if the disk is spun up or not. Sounds like very little work to me
if you have the hdparm and update source.

-- 
[======================================================================]
[     Kevin Lentin               Email: K.Lentin@cs.monash.edu.au      ]
[   finger kevinl@fangorn.cs.monash.edu.au for PGP public key block.   ]
[  KeyId: 06808EED    FingerPrint: 6024308DE1F84314  811B511DBA6FD596  ]
[======================================================================]


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu