From owner-freebsd-hackers Tue Feb 16 11:51:44 1999 Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26036 for ; Tue, 16 Feb 1999 11:51:37 -0800 (PST) (envelope-from bright@cygnus.rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.8.7/8.8.7) with SMTP id OAA11455; Tue, 16 Feb 1999 14:20:46 -0500 (EST) Date: Tue, 16 Feb 1999 14:20:45 -0500 (EST) From: perlsta To: Matthew Dillon cc: "John S. Dyson" , freebsd-hackers@FreeBSD.ORG Subject: Re: inode / exec_map interlock ? (follow up) In-Reply-To: <199902161808.KAA37094@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Feb 1999, Matthew Dillon wrote: > :John S. Dyson said: > :> Matthew Dillon said: > :> > > :> > The ORIGINAL VM CODE. Do I need to repeat that? The *ORIGINAL* VM CODE > :> > does not have one single line of source to prevent excessive queueing > :> > of I/O for pageout ops. > :> > > :> You are wrong. Please look at the code. I will point the code out to you > :> if you want, but I suspect that you don't want to know. > :> > :Please refer to the message that I sent to you on 10 Jan 99 for some more > :information in that arena. Apparently you didn't listen -- and what I > :said describes essentially what the nastier (but correctly working) > :swap pager does. > : > :I even explained to you in terms of "clogging" the I/O subsystem and blindly > :freeing pages. That is a *very* real problem, and the old swap pager largely > :stopped that from happening. Maybe this isn't the gretest time to jump in with a question, but i'm interested in the working of the former and current systems. I've noticed that the 'old' swapper or system seemed to leave a LOT of swap still used en it wasn't trully needed. The new system seems to reclaim these regeons as soon as they are swapped in. I've noticed the new swapper is a bit more 'peppy' but i'm concerned that it is dooing what John says. What's the deal here? Matt, even though your swapper lists pages as 'free' does it actually keep them around for reuse? What happens when a page is READ faulted in, is the backing swap kept allocated to save on IO later? One other thing, I has some trouble getting to sleep last night and decided to venture into src/sys/vm, the comments are VERY helpful. The kind of documentation going on here will really help people get into systems programming, it is MUCH appreciated. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message