summaryrefslogtreecommitdiffstats
path: root/sys/sys/resourcevar.h
diff options
context:
space:
mode:
authortjr <tjr@FreeBSD.org>2003-02-20 04:18:42 +0000
committertjr <tjr@FreeBSD.org>2003-02-20 04:18:42 +0000
commit569e9d1a868a053312375c90c3f0c7ab35d18e47 (patch)
tree28ed51036df7221547d852601de750f3a017c7e6 /sys/sys/resourcevar.h
parentc812b91a675fc33d56c494228f512aef76f65480 (diff)
downloadFreeBSD-src-569e9d1a868a053312375c90c3f0c7ab35d18e47.zip
FreeBSD-src-569e9d1a868a053312375c90c3f0c7ab35d18e47.tar.gz
Remove the PL_SHAREMOD flag from struct plimit, which could have been
used to share resource limits between rfork threads, but never was. Removing it makes resource limit locking much simpler -- only the current process can change the contents of the structure that p_limit points to.
Diffstat (limited to 'sys/sys/resourcevar.h')
-rw-r--r--sys/sys/resourcevar.h7
1 files changed, 1 insertions, 6 deletions
diff --git a/sys/sys/resourcevar.h b/sys/sys/resourcevar.h
index 572b575..40db407 100644
--- a/sys/sys/resourcevar.h
+++ b/sys/sys/resourcevar.h
@@ -72,15 +72,10 @@ struct pstats {
/*
* Kernel shareable process resource limits. Because this structure
* is moderately large but changes infrequently, it is normally
- * shared copy-on-write after forks. If a group of processes
- * ("threads") share modifications, the PL_SHAREMOD flag is set,
- * and a copy must be made for the child of a new fork that isn't
- * sharing modifications to the limits.
+ * shared copy-on-write after forks.
*/
struct plimit {
struct rlimit pl_rlimit[RLIM_NLIMITS];
-#define PL_SHAREMOD 0x01 /* modifications are shared */
- int p_lflags;
int p_refcnt; /* number of references */
};
OpenPOWER on IntegriCloud