| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Obtained from: Linux
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
as a result of the hints mechanism.
|
|
|
|
|
|
|
|
| |
Enhanced SpeedStep (that is, a follow-up of it called Foxton). Until
we actually have support for that, we build to catch regressions in
the framework.
Triggered by: njl
|
| |
|
|
|
|
| |
Requested by: marcus
|
|
|
|
|
|
|
| |
acces to tap(4) device nodes based on file system permission.
Duplicate the 'debug.if_tap_debug' sysctl under the
'net.link.tap' hierarchy.
|
|
|
|
|
|
|
|
| |
- Add unp_addsockcred() (for LOCAL_CREDS).
- Add an argument to unp_connect2() to differentiate between
PRU_CONNECT and PRU_CONNECT2. (for LOCAL_CONNWAIT)
Obtained from: NetBSD (with some changes)
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
operations in some places and simple non-per CPU math in others.
|
|
|
|
| |
variable.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
3ware's 9xxx series controllers. This corresponds to
the 9.2 release (for FreeBSD 5.2.1) on the 3ware website.
Highlights of this release are:
1. The driver has been re-architected to use a "Common Layer"
(all tw_cl* files), which is a consolidation of all OS-independent
parts of the driver. The FreeBSD OS specific portions of the
driver go into an "OS Layer" (all tw_osl* files).
This re-architecture is to achieve better maintainability, consistency
of behavior across OS's, and better portability to new OS's (drivers
for new OS's can be written by just adding an OS Layer that's specific
to the OS, by complying to a "Common Layer Programming Interface" API.
2. The driver takes advantage of multiple processors.
3. The driver has a new firmware image bundled, the new features of which
include Online Capacity Expansion and multi-lun support, among others.
More details about 3ware's 9.2 release can be found here:
http://www.3ware.com/download/Escalade9000Series/9.2/9.2_Release_Notes_Web.pdf
Since the Common Layer is used across OS's, the FreeBSD specific include
path for header files (/sys/dev/twa) is not part of the #include pre-processor
directive in any of the source files. For being able to integrate twa into
the kernel despite this, Makefile.<arch> has been changed to add the include
path to CFLAGS.
Reviewed by: scottl
|
|
|
|
| |
using the existing clock_lock mutex.
|
|
|
|
| |
- Simplify conditional logic to make code easier to read.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1 Move the debug.clock_adjust_* sysctls to debug.clock.adjust_* to
make it easier to get only the clock statistics.
2 Make the sysctls read-only [suggested by Marius].
3 When determining the new clock adjustment, we checked for an error
either larger than 12.5% or smaller than 12.5%. We left out an error
of exactly 12.5%. For errors larger than 12.5% we adjust the clock
reload value in such a way that the next clock interrupt would be
early (as in premature). For errors less than 12.5% we stopped the
adjustment.
The current algorithm doesn't benefit from excluding an error of
exactly 12.5%. Change the code to stop adjusting the clock if the
error is *not* larger than 12.5% [suggested by Marius].
Discussed with: marius@
|
|
|
|
| |
Reviewed by: Tai-hwa Liang
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o don't pre-assign key index to the global key table entries so device
has a chance to decide what to use
o make ieee80211_crypto_newkey take the desired flags as an argument
instead of wacking the key structure directly; this eliminates a
bunch of code warts
o add a new flag IEEE80211_KEY_GROUP to indicate a key is a WPA Group
key so devices don't need to guess (temporarily add this flag in the
ioctl code until we can get wpa_supplicant+hostapd updated)
o shuffle IEEE80211_KEY_* bits to move flags used internally to the high
nibble of the flags word
Reviewed by: Tai-hwa Liang
|
|
|
|
| |
Approved by: grehan (mentor)
|
|
|
|
|
|
|
|
|
|
| |
problems here, it became clear we were being too complex.
o Don't keep track of resources in two places
o Use resource_list_purge instead of rolling our own
o Just reassign the ownership of the resource, rather than freeing it
and reallocating it.
o Fix compile problems when sizeof(u_long) != sizeof(int)
|
| |
|
|
|
|
|
|
| |
elements of this list (eg, reset it).
Man page to follow
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
in BSD and MBR classes, ie. if provider below us uses the same metadata,
don't create labels based on the metadata.
This allows to create labels on geoms with rank != 1 without hacks.
Tested by: Chris Elsworth <chris@shagged.org> on sparc64
OK'ed by: phk
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
this code:
o rid is stored in the resource, so don't bother keeping track of it here.
o Implement memory space
o Don't try to activate 'memory card' CFEs. This is type memory, as opposed
to the memory resource.
|
| |
|
|
|
|
| |
on here.
|
|
|
|
|
|
|
|
|
|
|
|
| |
resource_list_find. Check to make sure that rle is not NULL and panic
if it is (but it appears that resource_list_add already panics, so I'm
not entirely sure it is necessary now).
Add a test to make sure we have a interrupt resource when we're
disabling it. This is also a cannot happen, but the extra care
shoudln't hurt.
Found by: Coventry tool via sam@
|
|
|
|
|
|
|
| |
resouce_list_find in some places.
Suggested by: sam
Found by: Coventry Analysis tool.
|
|
|
|
| |
Pointy hat to: me
|
|
|
|
|
|
|
|
|
|
| |
whether or not the receive pipe is stopped. This ensures that we
do not attempt to start the same transfer twice, and it allows
ucomstop() to skip the restarting of the read pipe if it was not
originally running, such as when called indirectly from ucomreadcb().
PR: kern/79420
MFC after: 1 day
|
|
|
|
| |
the previous commit.
|
| |
|
|
|
|
|
| |
wrappers by pushing them onto the stack rather than keeping them in %esi
and %edi.
|
| |
|
|
|
|
|
|
|
|
|
| |
with E may be called with a shared lock held. This list really could
be made per filesystem if we had any filesystems which differed from
ffs in locking guarantees. VFS itself is not sensitive to this except
where vgone() etc. are concerned.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
| |
uses it.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
|
| |
the VOP requires an exclusive lock.
Sponsored by: Isilon Systems, Inc.
|
|
|
|
|
| |
that it's possible to build a kernel without getting flooded with
thousands of warnings.
|