Move maxdmap and maxsmap where they belong and make them big enough.

This commit is contained in:
eeh 2001-02-06 19:54:43 +00:00
parent cb428a8601
commit ec22628573
2 changed files with 11 additions and 6 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: kern_resource.c,v 1.59 2000/08/20 21:50:11 thorpej Exp $ */ /* $NetBSD: kern_resource.c,v 1.60 2001/02/06 19:54:43 eeh Exp $ */
/*- /*-
* Copyright (c) 1982, 1986, 1991, 1993 * Copyright (c) 1982, 1986, 1991, 1993
@ -54,6 +54,15 @@
#include <uvm/uvm_extern.h> #include <uvm/uvm_extern.h>
/*
* Maximum process data and stack limits.
* They are variables so they are patchable.
*
* XXXX Do we really need them to be patchable?
*/
rlim_t maxdmap = MAXDSIZ;
rlim_t maxsmap = MAXSSIZ;
/* /*
* Resource controls and accounting. * Resource controls and accounting.
*/ */
@ -236,7 +245,6 @@ dosetrlimit(p, cred, which, limp)
struct rlimit *limp; struct rlimit *limp;
{ {
struct rlimit *alimp; struct rlimit *alimp;
extern unsigned maxdmap, maxsmap;
struct plimit *newplim; struct plimit *newplim;
int error; int error;

View File

@ -1,4 +1,4 @@
/* $NetBSD: uvm_glue.c,v 1.43 2000/11/25 06:27:59 chs Exp $ */ /* $NetBSD: uvm_glue.c,v 1.44 2001/02/06 19:54:44 eeh Exp $ */
/* /*
* Copyright (c) 1997 Charles D. Cranor and Washington University. * Copyright (c) 1997 Charles D. Cranor and Washington University.
@ -97,9 +97,6 @@ static void uvm_swapout __P((struct proc *));
* XXXCDC: do these really belong here? * XXXCDC: do these really belong here?
*/ */
unsigned maxdmap = MAXDSIZ; /* kern_resource.c: RLIMIT_DATA max */
unsigned maxsmap = MAXSSIZ; /* kern_resource.c: RLIMIT_STACK max */
int readbuffers = 0; /* allow KGDB to read kern buffer pool */ int readbuffers = 0; /* allow KGDB to read kern buffer pool */
/* XXX: see uvm_kernacc */ /* XXX: see uvm_kernacc */