From owner-freebsd-hackers Fri Jan 22 15:53:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04306 for freebsd-hackers-outgoing; Fri, 22 Jan 1999 15:53:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from iquest3.iquest.net (iquest3.iquest.net [209.43.20.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA04299 for ; Fri, 22 Jan 1999 15:53:34 -0800 (PST) (envelope-from toor@y.dyson.net) Received: (qmail 8225 invoked from network); 22 Jan 1999 23:53:18 -0000 Received: from dyson.iquest.net (HELO y.dyson.net) (198.70.144.127) by iquest3.iquest.net with SMTP; 22 Jan 1999 23:53:18 -0000 Received: (from root@localhost) by y.dyson.net (8.9.1/8.9.1) id SAA36870; Fri, 22 Jan 1999 18:53:18 -0500 (EST) Message-Id: <199901222353.SAA36870@y.dyson.net> Subject: Re: Error in vm_fault change In-Reply-To: <199901222344.QAA12241@usr09.primenet.com> from Terry Lambert at "Jan 22, 99 11:44:35 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 22 Jan 1999 18:53:18 -0500 (EST) Cc: dillon@apollo.backplane.com, dyson@iquest.net, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert said: > > I think the RSS fix is needlessly complex. I offer a suggestion > that is vastly simpler, amenable to policy exception via madvise, > and otherwise altogether more in line with a real soloution to the > problem. > Actually, the RSS code has been in the kernel for about 3yrs now, and is well understood. If it was being written from scratch, I would be more likely to agree with you. The kernel RSS limiting code works mostly for private data in the process. > > What I suggest is that vnodes with more than a certain number of > pages associated with them be forced to steal pages from their > own usage, instead of obtaining them from the system page pool. > Vnodes aren't the only structure that contains data -- maybe you mean vm objects also. In fact, vnode or "shared" data isn't usually the problem with memory usage. However a vnode quota is probably a good idea also. > > In general, when we talk about badly behaved processes, we are > talking about processes with large working sets that are directly > mapped to vnode backing objects. > Not necessarily, think the new versions of GNU C++ :-). > > This soloution was tried, and worked very well, in a UnixWare 2.0 > kernel > No UnixWare kernel VM ever worked very well, did it? -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message