Subject: Re: lazy mlock?
To: <>
From: David Laight <>
List: tech-kern
Date: 04/16/2002 23:48:32
On Tue, Apr 16, 2002 at 11:03:15PM +0100, Richard Earnshaw wrote:
> The problem was that ntpd was locking about 6M of RAM (~20%) down and 
> killing that solved most of the thrashing issues.

If it isn't a silly question, why should ntpd 'lock down' any code at all?


David Laight: