| Age | Commit message (Collapse) | Author |
|---|
|
which is used to size a zillion other things that increasing excessively
has been shown to cause problems - so that we may incrementally look at
increasing those other things without making the kernel unusable.
This diff effectivly increases the number of vnodes back to the number
of buffers, as in the earlier dynamic buffer cache commits, without
increasing anything else (namecache, softdeps, etc. etc.)
ok pedro@ tedu@ art@ thib@
|
|
Pick reasonble names for the locks involved..
ok tedu@, art@
|
|
have cpu_info now, so kill the option.
eyeballed by jsg@ and grange@
|
|
to wire more memory than we are allowed to.
miod@ ok
|
|
leave macros behind for now to keep the commit small
ok art beck miod pedro
|
|
of new fields in the future is less disruptive. This is done similar
to how struct proc is handled for ps(1). ok jmc (man page changes)
tested fkr simon, and more suggestions from millert
|
|
spotted by art, ok dlg art
|
|
In this commit:
- gdt lock on amd64
- sysctl lock
- malloc sysctl lock
- disk sysctl lock
- swap syscall lock
miod@, pedro@ ok (and "looks good" others@)
|
|
Constantine A. Murenin
|
|
errors to userland: make all cpu_setperf functions return void.
Tested by many, ok gwk@
|
|
the higher level sysctl code passing them to userland. Distinct diff from
the one I passed around internally with less crazy semantics. Also nuke
some trailing spaces in a few places.
"just go ahead" deraadt@
|
|
should never be referenced outside the context of the process to which
this stack belongs unless we do the PHOLD/PRELE dance. Loads of code
doesn't follow the rules here. Instead of trying to track down all
offenders and fix this hairy situation, it makes much more sense
to not swap kernel stacks.
From art@, tested by many some time ago.
|
|
copying out to userland, so my fix was useless bloat that didnt really do
anything. the problem instead appears to be a use after free in a driver
rather than bad interactions with sysctl.
|
|
copied out to userland. If this happens we get a use after free and things
blow up. Prevent this by making a local copy of the sensor that cannot be
freed elsewhere in the kernel and copying that out instead.
found by mbalmer@
ok deraadt@ krw@
|
|
hook up some sysctls to add system vendor/product/version and UUID reporting.
"get it in" deraadt@
|
|
variable if the result is a lowering of the value; tested matthieu
|
|
locating and finding the correct sensor to spit out. instead provide a
a sensor_get function that wraps up the access to the vars. theyre now
safe inside kern_sensors.c.
theres also a touch of whitespace tweaking
ok grange@
|
|
sensor_add()/sensor_del() so that sensors can be attached
and detached dynamicaly.
ok kettenis@ deraadt@ dlg@
|
|
'go for it' deraadt@
|
|
collisions with local variable names someone might make. this has bitten
me twice now and caused me to lose about 4 hours scratching my head when
nsensors just magically corrupts and gets bigger. at least my ram isnt
screwed.
ok marco@
|
|
of panics and bugfixes. Access curproc directly, do not expect a process
pointer as an argument. Should fix many "process context required" bugs.
Incentive and okay millert@, okay marc@. Various testing, thanks.
|
|
tested on GENERIC and RAMDISK_CD to see if the small_kernel stuff stays
happy
|
|
the protection of the memory mapping we're doing I/O on, or if we want to
leave them as they are. This should only be necessary for breakpoint
insertion in code, so we'll only use it for ptrace requests.
Initially from art@ after discussion with kettenis@ millert@ and I,
tested by many.
|
|
instead of the contents of a for() loop. No functional change.
From the m88k SMP tree; ok art@ deraadt@
[complete diff this time]
|
|
|
|
instead of the contents of a for() loop. No functional change.
From the m88k SMP tree; ok art@ deraadt@
|
|
allocate them on startup if needed, and free them when done.
discussion with pascoe, tested by dlg
|
|
spc_cp_time member of struct schedstate_percpu (per-cpu stats).
From art@ during the hackathon.
|
|
ok + input deraadt miod
|
|
pages a process uses. this is now the userland "data size" value.
ok art deraadt tdeval. thanks testers.
|
|
restrict lock count per uid to a global limit, add sysctl to adjust limit.
this prevents a user from creating too many locks. problem noticed
by devon o'dell. ok deraadt miod pedro
|
|
HW_SENSORS sysctl trees if option SMALL_KERNEL.
ok deraadt@
|
|
|
|
|
|
|
|
ok millert@
|
|
code is all conditionalized on __HAVE_TIMECOUNTER, and not
enabled on any platforms.
adjtime(2) support exists, courtesy of nordin@, sysctl(2) support
and a concept of quality for each time source attached exists.
High quality time sources exists for PIIX4 ACPI timer as well as
some AMD power management chips. This will have to be redone
once we actually add ACPI support (at that time we need to use
the ACPI interfaces to get at these clocks).
ok art@ ken@ miod@ jmc@ and many more
|
|
with modifications from me. Includes code for generic interrupt counter
fetching via sysctl. deraadt@ tholo@ drahn@ millert@ ok
|
|
translates a cpu_info structure into a human-readable cpu number.
drahn@ deraadt@ ok
|
|
Add trivial support for passing a NULL pointer for the argv buffer;
currently just returns ARG_MAX for KERN_PROC_ARGV and KERN_PROC_ENV.
|
|
Found by otto@drijf.net
deraadt@ ok
|
|
|
|
|
|
Introduce the cpu_info structure, p_cpu field in struct proc and global
scheduling context and various changed code to deal with this. At the
moment no architecture uses this stuff yet, but it will allow us slow and
controlled migration to the new APIs.
All new code is ifdef:ed out.
ok deraadt@ niklas@
|
|
remove alpha specific definition of ncpus.
OK (and tested on alpha) deraadt@
|
|
update cpu even with 100 -> 100 setperf changes, in case saved value
has gotten out of sync. from grange@ ok deraadt@ grange@
|
|
|
|
from form@pdp-11.org.ru via mpech. ok millert
|
|
an interrupt safe thread.
use this as the new backend for mbpool and mclpool, eliminating the mb_map.
introduce a sysctl kern.maxclusters which controls the limit of clusters
allocated.
testing by many people, works everywhere but m68k. ok deraadt@
this essentially deprecates the NMBCLUSTERS option, don't use it.
this should reduce pressure on the kmem_map and the uvm reserve of static
map entries.
|
|
separate exec format from emulation. consistent naming of freebsd emuls.
not much in the way of functional changes yet.
testing and ok deraadt@ and others along the way.
|
