| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which is initialized with whatever string a dhcp/bootp server passes
as vendor tag 134.
There is no standard tag that I know with this information, and
no vendor-defined tag that applies to FreeBSD that I could find
doing the same thing.
The intended use is to pass information to userland for run-time
configuration of a diskless client without having to run a bootp/dhcp
client for the third time (after the one in pxeboot/etherboot, and
the one in the kernel bootp), also because these clients generally
screwup the interface configuration, which is not exactly what you
want when you have your disks nfs-mounted.
Manpage update to follow soon.
MFC-after: 3 days
|
| |
|
|
|
|
| |
work like an NMI button.
|
| |
|
|
|
|
|
| |
that I introduced with -v. However, other problems still remain (including
the loss of interrupts).
|
|
|
|
|
|
| |
Stop the other cpus when shutting down or entering the debugger.
Submitted by: tmm
|
|
|
|
| |
Submitted by: tmm
|
|
|
|
| |
Submitted by: tmm
|
|
|
|
|
| |
on return to user mode. We may not have frame pointers setup for more
than 1 on return from exec.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
wait for those cpus, instead of all of them by using a count. Oops.
Make the pointer to the mask that the primary cpu spins on volatile, so
gcc doesn't optimize out an important load. Oops again.
Activate tlb shootdown ipi synchronization now that it works. We have
all involved cpus wait until all the others are done. This may not be
necessary, it is mostly for sanity.
Make the trigger level interrupt ipi handler work.
Submitted by: tmm
|
|
|
|
| |
Submitted by: tmm
|
| |
|
|
|
|
|
| |
Submitted by: tmm
Forgotten by: obrien
|
|
|
|
| |
Reviewed by: alfred
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
acquire shared locks on leafs.
The stat() and open() calls have been changed to make use of this new functionality. Using shared locks in
these cases is sufficient and can significantly reduce their latency if IO is pending to these vnodes. Also,
this reduces the number of exclusive locks that are floating around in the system, which helps reduce the
number of deadlocks that occur.
A new kernel option "LOOKUP_SHARED" has been added. It defaults to off so this patch can be turned on for
testing, and should eventually go away once it is proven to be stable. I have personally been running this
patch for over a year now, so it is believed to be fully stable.
Reviewed by: jake, obrien
Approved by: jake
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Later gcc's blow up on this.
|
| |
|
|
|
|
| |
which is 64 bit on ia64. Fix it.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
test and play with this.
This is not yet production quality and should be run only on dedicated
test boxes.
For people who want to develop transformations for GEOM there exist a
set of shims to run geom in userland (ask phk@freebsd.org).
Reports of all kinds to: phk@freebsd.org
Please include in report:
dmesg
sysctl debug.geomdot
sysctl debug.geomconf
Known significant limitations:
no kernel dump facility.
ioctls severely restricted.
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
| |
the ATA/ATAPI driver. This solves the concurrency problem with
the new GEOM code, and also cuts a good deal of the patch size
in the upcoming MFC.
|
|
|
|
| |
Noticed by: bmilekic
|
|
|
|
| |
Noticed by: wilko, mjacob, jhb, peter, and others
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
update the free-space statistics in some cases. The problem affected
directory blocks when the free space dropped below the size of the
maximum allowed entry size. When this happened, the free-space
summary information could claim that there are no further blocks
that can fit a maximum-size entry, even if there are.
The effect of this bug is that the directory may be enlarged even
though there is space within the directory for the new entry. This
wastes disk space and has a negative impact on performance.
Fix it by correctly computing the dh_firstfree array index, adding
a helper macro for clarity. Put an extra sanity check into
ufsdirhash_checkblock() to detect the situation in future.
Found by: dwmalone
Reviewed by: dwmalone
MFC after: 1 week
|
| |
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
| |
the cdev switch.
|
|
|
|
|
|
|
|
|
|
|
| |
read-only.
The trouble here is that we don't reopen the device in read/write mode
when we remount in read/write mode resulting in a filesystem sending
write requests to a device which was only opened read/only.
I'm not quite sure how such a reopen would best be done and defer
the problem to more agile hackers.
|
|
|
|
|
|
|
| |
It was used to initialize an unused variable, because ext2fs was
copy&pasted from UFS rather than copy,paste&cleaned from UFS.
Suggested by: bde
|
|
|
|
|
|
|
|
|
| |
unit allocation with a bitmap in the generic layer. This
allows us to get rid of the duplicated rman code in every
clonable interface.
Reviewed by: brooks
Approved by: phk
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Sneak in a trivial bit of the GEOM stuff while we're here anyway.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Spotted by: David Wolfskill <david@catwhisker.org>
Investigated by: rwatson
|
| |
|
|
|
|
| |
we must now explicitly list the source directory with -I.
|
| |
|
| |
|
|
|
|
| |
the argument.
|