Date: Sun, 21 Jul 2002 19:10:07 -0700 From: Mike Makonnen <makonnen@pacbell.net> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-smp@FreeBSD.org, bright@mu.org Subject: Re: Getting resource limits out from under Giant Message-ID: <20020721191007.7aa7cf4e.makonnen@pacbell.net> In-Reply-To: <XFMail.20020715090314.jhb@FreeBSD.org> References: <20020713222131.6ebf07c8.makonnen@pacbell.net> <XFMail.20020715090314.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Jul 2002 09:03:14 -0400 (EDT) John Baldwin <jhb@FreeBSD.org> wrote: > > > At this early stage (relatively) I would prefer to get it working cleanly > and optimize it later, but that's just me. > Ok. Done. I've worked on it some more. I think I've caught all the areas in the code that touch or read limits. The new patch is up at: http://home.pacbell.net/makonnen/limits.tar.gz The tarball contains three patches. The first one adds the limit locking infrastructure to the kernel, the second one locks down all references to limits. If the limit structure is being modified or the code requires a stable reference over several lines of code, the locks both the proc and limit. If the code just dereferences the limit structure, then it just locks the proc structure. The third patch removes giant from the relevant code. However, I left it in place in some instances because I was not sure whether the code still required it or not. Cheers, Mike Makonnen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020721191007.7aa7cf4e.makonnen>