summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* when calling ldd, use the cross libraries and not the host versionluigi2009-12-091-4/+4
| | | | MFC after: 3 days
* use default HZluigi2009-12-091-1/+1
|
* add -lulog, the program "less" and a commentluigi2009-12-091-1/+4
|
* Clear result before requesting XPT_PATH_INQ.mav2009-12-091-0/+1
| | | | Many SIMs doesn't fill maxio field yet.
* Increase Max Read Request Size for PCIe chips from 512 to 1024 bytes.mav2009-12-091-1/+14
| | | | It gives those beasts additional 10% of write bandwidth.
* The default balance algorithm has changed from "split" toru2009-12-091-2/+2
| | | | (the improved version of) "load".
* make PV core dump actually dump memory - still need to fix program header ↵kmacy2009-12-092-0/+7
| | | | initialization
* Allow using IPv6 in nfsrvd_sentcache() callback.delphij2009-12-081-2/+3
| | | | | | | PR: kern/141289 Submitted by: Petr Lampa <lampa fit vutbr cz> Approved by: rmacklem MFC after: 1 week
* Change gmirror default balance algorithm from "split" to "load".mav2009-12-081-1/+1
| | | | | | | | | | | "split" is very ineffective for devices with rotating media as HDDs. To be effective, it needs that transfer time reduction due to block splitting was bigger then access time increase due to non-sequential access. For modern HDDs I was able to reproduce it only with read sizes of 2MB and above, which is almost not applicable in real life. "load" algorithm same time is more universal and effective now. Reviewed by: pjd
* Simplify a macro not to generate unncessary symbols.jkim2009-12-081-14/+1
|
* Fix the build.mav2009-12-081-2/+13
|
* sem_init(3): document process shared semaphores and their restrictionsjilles2009-12-081-18/+9
|
* Don't add VAPPEND if the file is not being opened for writing. Note that thistrasz2009-12-082-2/+2
| | | | | | | only affects cases where open(2) is being used improperly - i.e. when the user specifies O_APPEND without O_WRONLY or O_RDWR. Reviewed by: rwatson
* Add additional checks of the kernel stack addresses in order tomarius2009-12-082-6/+22
| | | | | | ensure we don't overrun the end of the call chain. MFC after: 1 week
* What we have in base system is actually OpenBSD 4.5's netcat,delphij2009-12-081-1/+1
| | | | update this file to reflect the fact.
* Remove phantom line of code that somehow slippedjfv2009-12-081-1/+0
| | | | into the checkin.
* Create sysctl node(dev.bge.%d.focred_collapse) instead ofyongari2009-12-082-21/+25
| | | | | | | | | hw.bge.forced_collapse. hw.bge.forced_collapse affects all bge(4) controllers on system which may not desirable behavior of the sysctl node. Also allow the sysctl node could be modified at any time. Reviewed by: bde (initial version)
* Add ID for NetMos NM9820 Serial Port chip, found on CardBus serial adapter.mav2009-12-081-0/+1
|
* MFi386: revision 200219nyan2009-12-082-8/+25
| | | | | | | Improve the algorithm the loader uses to choose a memory range for its heap when using a range above 1MB. MFC after: 1 week
* MFi386: Use real mode instead of v86 mode.nyan2009-12-081-410/+361
| | | | MFC after: 1 week
* MFi386: revision 200216nyan2009-12-082-3/+2
| | | | Various small whitespace and style fixes.
* - Try pre-allocating all FIBs upfront. Previously we tried pre-allocatingjkim2009-12-083-10/+6
| | | | | | | | | | | 128 FIBs first and allocated more later if necessary. Remove now unused definitions from the header file[1]. - Force sequential bus scanning. It seems parallel scanning is in fact slower and causes more harm than good[1]. Adjust a comment to reflect that. PR: kern/141269 Submitted by: Alexander Sack (asack at niksun dot com)[1] Reviewed by: scottl
* Partially revert r200228. For mini RCB case, bge(4) still have toyongari2009-12-081-7/+5
| | | | | | | disable mini ring withtout regard to mini ring support. Reported by: marcel Tested by: marcel
* Resync with Intel versions of both the em and igbjfv2009-12-0822-1798/+3148
| | | | | | | | | | | drivers. These add new hardware support, most importantly the pch (i5 chipset) in the em driver. Also, both drivers now have the simplified (and I hope improved) watchdog code. The igb driver uses the new RX cleanup that I first implemented in ixgbe. em - version 6.9.24 igb - version 1.8.4
* Fix typo in commentrpaulo2009-12-081-1/+1
| | | | Submitted by: Paul B Mahol <onemda at gmail.com>
* Improve response to multi-touch taps.rpaulo2009-12-081-48/+117
| | | | Submitted by: Rohit Grover <rgrover1 at gmail.com>
* In exception_save, write-back ar.rnat after switching the backing-marcel2009-12-081-14/+13
| | | | | | | store. Writing to ar.bspstore is defined to leave ar.rnat undefined. PR: ia64/120315 MFC after: 3 days
* Update driver to Intel version 2.0.7:jfv2009-12-0712-1269/+2510
| | | | | | | | | | | | | | | | | | | | | This adds new feature support for the 82599, a hardware assist to LRO, doing this required a large revamp to the RX cleanup code because the descriptor ring may not be processed out of order, this necessitated the elimination of global pointers. Additionally, the RX routine now does not refresh mbufs on every descriptor, rather it will do a range, and then update the hardware pointer at that time. These are performance oriented changes. The TX side now has a cleaner simpler watchdog algorithm as well, in TX cleanup a read of ticks is stored, that can then be compared in local_timer to determine if there is a hang. Various other cleanups along the way, thanks to all who have provided input and testing.
* Revert r200231. It was already taken cared by jhb long ago.jkim2009-12-071-16/+3
| | | | | Pointed out by: jhb Pointy hat: jkim
* Make mfi(4) little bit less chatty.jkim2009-12-071-3/+16
|
* Add support for the NetMos NM9865 family of Serial/Parallel ports.marcel2009-12-072-3/+40
| | | | | Obtained from: NetMos MCS9865 v1.0.0.1 driver MFC after: 3 days
* Don't access jumbo frame related registers if controller lacks theyongari2009-12-071-8/+14
| | | | | | | | | feature. These registers are reserved on controllers that have no support for jumbo frame. Only BCM5700 has mini ring so do not poke mini ring related registers if controller is not BCM5700. Reviewed by: marius
* Remove PHY isolate/power down code in bge_stop(). The isolationyongari2009-12-071-27/+0
| | | | | | | | | | | handler in brgphy(4) does not exist and brgphy(4) just resets the PHY and returns EINVAL as it has no isolation handler. I also agree on Marius's opinion that stop handler of every NIC driver seems to be the wrong place for implementing PHY isolate/power down. If we need PHY isolate/power down it should be implemented in brgphy(4) and users should administratively down the PHY. Reviewed by: marius
* Explicitly acknowledge MSI completion, as required by SiI3124 datasheet.mav2009-12-072-3/+14
| | | | | | It makes MSI working there. Later (and cheaper) PCIe chips (3132/3531) still randomly crashing system in few seconds of high MSI rates, generating something inaporopriate, like NMI or "Fatal trap 30".
* Improve the algorithm the loader uses to choose a memory range for itsjhb2009-12-073-8/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | heap when using a range above 1MB. Previously the loader would always use the last 3MB in the first memory range above 1MB for the heap. However, this memory range is also where the kernel and any modules are loaded. If this memory range is "small", then using the high 3MB for the heap may not leave enough room for the kernel and modules. Now the loader will use any range below 4GB for the heap, and the logic to choose the "high" heap region has moved into biosmem.c. It sets two variables that the loader can use for a high heap if it desires. When a high heap is enabled (BZIP2, FireWire, GPT, or ZFS), then the following memory ranges are preferred for the heap in order from best to worst: - The largest memory region in the SMAP with a start address greater than 1MB. The memory region must be at least 3MB in length. This leaves the region starting at 1MB purely for use by the kernel and modules. - The last 3MB of the memory region starting at 1MB if it is at least 3MB in size. This matches the current behavior except that the current loader would break horribly if the first region was not at least 3MB in size. - The memory range from the end of the loader up to the 640k window. This is the range the loader uses when none of the high-heap-requesting options are enabled. Tested by: hrs MFC after: 1 week
* MFp4;mav2009-12-073-14/+23
| | | | | | - Cleanup kernel messages, mostly PMP. - Took references on devices, while PMP reinitializes them, to not let them go and distort freeze reference counting.
* SiI3124 has no SNotification register. Handle Asynchronous Notificationsmav2009-12-072-12/+27
| | | | there without it as good as possible.
* Various small whitespace and style fixes.jhb2009-12-073-10/+11
|
* Add <machine/pcb.h> missed in r199135.marius2009-12-071-0/+1
|
* Fix ntfs such that it understand media with a non-512-bytes sector size:guido2009-12-073-7/+15
| | | | | | | | | | 1. Fixups are always done on 512 byte chunks (in stead of sectors). This is kind of stupid. 2. Conevrt between NTFS blocknumbers (the blocksize equals the media sector size) and the bread() and getblk() blocknr (which are 512-byte sized) NB: this change should not affect ntfs for 512-byte sector sizes.
* Define struct pcpu_md as the only MD field of struct pcpu (pc_acpi_idmarcel2009-12-078-75/+81
| | | | | | | | | | excluded, as it's used by MI code) and mode the sysctl variables from pcpu_stats to pcpu_md. Adjust all references accordingly. While nearby, change the PCPU sysctl tree so that they match the CPU device sysctl tree -- they are now children of a static node called "machdep.cpu" and are named only with their cpu ID.
* Install libulog in /lib.ed2009-12-071-0/+2
| | | | | | | | | Because several applications in /bin use libulog (or may use it in the nearby future), it must not live inside /usr. It seems like we don't need to add the copy from /usr/lib to ObsoleteFiles.inc, because it's cleaned up during installation of libulog automatically. Reported by: ume
* Fix Read-After-Write (RAW) dependency violation for ar.ccv inmarcel2009-12-071-2/+2
| | | | | | | isc_atomic_xadd() and isc_atomic_cmpxchg(). Approved by: dougb@ MFC after: 1 week
* Allocate the VHPT for each CPU in cpu_mp_start(), rather thanmarcel2009-12-075-77/+75
| | | | | | | | | | | | | | allocating MAXCPU VHPTs up-front. This allows us to max-out MAXCPU without memory waste -- MAXCPU is now 32 for SMP kernels. This change also eliminates the VHPT scaling based in the total memory in the system. It's the workload that determines the best size of the VHPT. The workload can be affected by the amount of memory, but not necessarily. For example, there's no performance difference between VHPT sizes of 256KB, 512KB and 1MB when building the LINT kernel. This was observed with a system that has 8GB of memory. By default the kernel will allocate a 1MB VHPT. The user can tune the system with the "machdep.vhpt.log2size" tunable.
* Revert behavior change to setenv(), unsetenv() and putenv() until a morescf2009-12-071-3/+6
| | | | thorough security review has been completed.
* Add Asynchronous Notification support for controllers without SNTFmav2009-12-061-3/+12
| | | | | capability by snooping SDB FIS receive area. It should be even faster then regular way, but less reliable.
* Update the getenv(3) man page to reflect the recent change to the behaviorscf2009-12-061-9/+9
| | | | | | | of setenv(), putenv() and unsetenv() when dealing with corrupt entries in environ. They now output a warning and complete their task without error. MFC after: 1 week
* Register a request that all changes to *env(3) be reviewed by secteamcperciva2009-12-061-0/+2
| | | | prior to commit due to the problematic history of this code.
* sh: Test ;<newline> as well as ; in the 'for' parser test.jilles2009-12-061-3/+3
|
* Change the behavior of setenv(), putenv() and unsetenv() to continue parsingscf2009-12-061-6/+3
| | | | | | | | | | | | instead of returning an error if a corrupt (not a "name=value" string) entry in the environ array is detected when (re)-building the internal environment. This should prevent applications or libraries from experiencing issues arising from the expectation that these calls will complete even with corrupt entries. The behavior is now as it was prior to 7.0. Reviewed by: jilles MFC after: 1 week
OpenPOWER on IntegriCloud