summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* - add read only sysctl to indicate if write-combining was enabledgallatin2006-08-011-1/+7
| | | | | - enable mxge_dummy_rdma() right after reset, and make sure to disable when detaching the driver.
* Reimplement socket buffer tear-down in sofree(): as the socket is norwatson2006-08-013-27/+76
| | | | | | | | | | | | | longer referenced by other threads (hence our freeing it), we don't need to set the can't send and can't receive flags, wake up the consumers, perform two levels of locking, etc. Implement a fast-path teardown, sbdestroy(), which flushes and releases each socket buffer. A manual dom_dispose of the receive buffer is still required explicitly to GC any in-flight file descriptors, etc, before flushing the buffer. This results in a 9% UP performance improvement and 16% SMP performance improvement on a tight loop of socket();close(); in micro-benchmarking, but will likely also affect CPU-bound macro-benchmark performance.
* If skip_file_dev and skip_file_ino haven't been set (are still == 0),kientzle2006-08-011-1/+3
| | | | | | | then don't use them for testing for a recursive add. Thanks to: Spencer Minear MFC after: 7 days
* Correct spelling of 3DNow!.obrien2006-08-012-4/+4
|
* Close a race that occurs when using sendto() to connect and send on arwatson2006-07-311-2/+22
| | | | | | | | | | | | | | | | | | | | | UNIX domain socket at the same time as the remote host is closing the new connections as quickly as they open. Since the connect() and send() paths are non-atomic with respect to another, it is possible for the second thread's close() call to disconnect the two sockets as connect() returns, leading to the consumer (which plans to send()) with a NULL kernel pointer to its proposed peer. As a result, after acquiring the UNIX domain socket subsystem lock, we need to revalidate the connection pointers even though connect() has technically succeed, and reurn an error to say that there's no connection on which to perform the send. We might want to rethink the specific errno number, perhaps ECONNRESET would be better. PR: 100940 Reported by: Young Hyun <youngh at caida dot org> MFC after: 2 weeks MFC note: Some adaptation will be required
* Add some statistics that are needed to support RFC4188 as part of the SoC2006thompsa2006-07-314-1/+161
| | | | | | work on a bridge monitoring module for BSNMP. Submitted by: shteryana (SoC 2006)
* inetd and telnetd are not included in the standard releaseyar2006-07-312-0/+4
| | | | | | | crunched floppies, but they can be included as options in src/release/picobsd (omitted by default though.) Therefore preserve the RELEASE_CRUNCH knob in their Makefiles, but tell its real purpose in a comment.
* Note hardware supported by powerpc, based on GENERIC.brueffer2006-07-311-13/+13
|
* Mark two more items as merged.brueffer2006-07-312-4/+4
|
* Rather than print out a nice error message giving details sufficent to fixobrien2006-07-311-3/+5
| | | | | a 'ufs_dirbad' and then panicing (making it very hard to see the details), put them in the panic message itself.
* Trim an obsolete comment. ktrgenio() stopped doing crazy gymnastics whenjhb2006-07-311-9/+0
| | | | ktrace was redone to be mostly synchronous again.
* In 'od -c' mode, deal with printable but zero-width combiningjkoshy2006-07-311-1/+1
| | | | | | | | | | characters correctly. These characters are displayed "combined" with a space character. PR: misc/100215 Submitted by: "J.R. Oldroyd" <<fbsd AT opal.com>> Reviewed by: "J.R. Oldroyd" <<fbsd AT opal.com>> (revised patch) MFC after: 3 days
* Regen.yar2006-07-311-2/+4
|
* Tell the bitter truth that WITHOUT_GNU and WITHOUT_PAMyar2006-07-312-0/+2
| | | | don't have any effect now.
* Stop enforcing dependencies between MK_* options at Makefile level.yar2006-07-313-3/+6
| | | | All the dependencies are satisfied now in <bsd.own.mk>.
* telnetd(8) doesn't really go to the crunched floppies,yar2006-07-311-2/+0
| | | | | | so its Makefile needn't test for RELEASE_CRUNCH. Suggested by: ru
* Regen from src/tools/build/options.yar2006-07-311-8/+26
|
* Document some more src.conf(5) options:yar2006-07-313-0/+13
| | | | | | WITHOUT_GNU, WITHOUT_NS_CACHING, WITHOUT_PAM. Noticed by: src/tools/build/options/makeman
* Actually skip over undocumented options with "continue"yar2006-07-311-0/+1
| | | | | | to avoid artifacts in the manpage generated. Previously an orphaned paragraph on dependencies of such an option would appear.
* Do not forget to increment the input line counteryar2006-07-311-0/+1
| | | | | | | when reading a word spanning multiple lines. PR: bin/101094 MFC after: 5 days
* Granting the amount of misunderstanding the last change received,yar2006-07-311-1/+7
| | | | extend it with an example to clarify the point.
* Remove two unused variables.kientzle2006-07-311-6/+0
| | | | Thanks to: Stefan Farfeleder
* Add the bones for PowerPC release documentation. This has beenmarcel2006-07-3112-1/+152
| | | | derived from ia64.
* Add proc-ia64.sgml to SRCS (uncomment).marcel2006-07-311-1/+1
|
* Fix the following bugs in re(4)wpaul2006-07-302-40/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Correct the PCI ID for the 8169SC/8110SC in the device list (I added the macro for it to if_rlreg.h before, but forgot to use it.) - Remove the extra interrupt spinlock I added previously. After giving it some more thought, it's not really needed. - Work around a hardware bug in some versions of the 8169. When sending very small IP datagrams with checksum offload enabled, a conflict can occur between the TX autopadding feature and the hardware checksumming that can corrupt the outbound packet. This is the reason that checksum offload sometimes breaks NFS: if you're using NFS over UDP, and you're very unlucky, you might find yourself doing a fragmented NFS write where the last fragment is smaller than the minimum ethernet frame size (60 bytes). (It's rare, but if you keep NFS running long enough it'll happen.) If checksum offload is enabled, the chip will have to both autopad the fragment and calculate its checksum header. This confuses some revs of the 8169, causing the packet that appears on the wire to be corrupted. (The IP addresses and the checksum field are mangled.) This will cause the NFS write to fail. Unfortunately, when NFS retries, it sends the same write request over and over again, and it keeps failing, so NFS stays wedged. (A simple way to provoke the failure is to connect the failing system to a network with a known good machine and do "ping -s 1473 <badhost>" from the good system. The ping will fail.) Someone had previously worked around this using the heavy-handed approahch of just disabling checksum offload. The correct fix is to manually pad short frames where the TCP/IP stack has requested checksum offloading. This allows us to have checksum offload turned on by default but still let NFS work right. - Not a bug, but change the ID strings for devices with hardware rev 0x30000000 and 0x38000000 to both be 8168B/8111B. According to RealTek, they're both the same device, but 0x30000000 is an earlier silicon spin.
* Use NO_SHARED=YES to force a static link.marcel2006-07-301-1/+1
| | | | Pointed out by: ru@
* Pass BN_CTX to internal functions instead of allocating it internally.simon2006-07-301-27/+35
| | | | | | This allows msqrt() to only call BN_CTX_new() once intead of many times. Suggested and reviewed by: stefanf
* Conditionally include sys/mkdev.h on platforms (such as Solaris) that need it.kientzle2006-07-301-1/+4
| | | | | | While I'm here, correctly alphabetize 't' after 's'. Thanks to: VMiklos
* Conditionally include sys/mkdev.h on platforms (such as Solaris) that need it.kientzle2006-07-301-0/+3
| | | | Thanks to: VMiklos
* Resolve conflicts after import of OpenSSL 0.9.8b.simon2006-07-301-53/+215
| | | | | | | | This was missed the first time around since eng_padlock.c was not part of OpenSSL 0.9.7e and therefor did not have the v0_9_7e CVS tag used during original resolve of conflicts. Noticed by: Antoine Brodin <antoine.brodin@laposte.net>
* This script should probably have an enabling variable since it can producemckay2006-07-301-2/+4
| | | | | surprising results. For now, at least make it safe to boot the default kernel when /boot/kernel is already a symlink.
* o Kill unneeded assignment.maxim2006-07-301-1/+0
| | | | Obtained from: OpenBSD
* Use 'skip' when ignoring data in tar archives. This dramaticallykientzle2006-07-3011-11/+287
| | | | | | | | | | | | | | | | | | | | increases performance when extracting a single entry from a large uncompressed archive, especially on slow devices such as USB hard drives. Requires a number of changes: * New archive_read_open2() supports a 'skip' client function * Old archive_read_open() is implemented as a wrapper now, to continue supporting the old API/ABI. * _read_open_fd and _read_open_file sprout new 'skip' functions. * compression layer gets a new 'skip' operation. * compression_none passes skip requests through to client. * compression_{gzip,bzip2,compress} simply ignore skip requests. Thanks to: Benjamin Lutz, who designed and implemented the whole thing. I'm just committing it. ;-) TODO: Need to update the documentation a little bit.
* Don't mention 'pax' in the context of POSIX-1988, sincekientzle2006-07-291-5/+4
| | | | | | | | | pax wasn't introduced until the 1993 (?) revision. (I need to double-check when pax was introduced and clarify some of the history here. In particular, I should explain that the 'pax' standard now owns the 'ustar' format spec.)
* Remove mention of 'tp' format, since that support has beenkientzle2006-07-291-10/+0
| | | | | removed. (It was introduced experimentally and I have simply never had time to finish it.)
* Sync FREEBSD-Xlist with what was actually excluded from OpenSSL 0.9.8bsimon2006-07-291-0/+4
| | | | import.
* Add some rough notes on how to import a new OpenSSL version into thesimon2006-07-291-0/+42
| | | | FreeBSD base system. Parts are inspired by the OpenSSH upgrade notes.
* Document many of the sysctls in acpi. Bump the date on acpi_thermal.4njl2006-07-292-9/+91
| | | | | | because I forgot to on the last change. MFC after: 1 day
* Add a new sysctl, hw.acpi.handle_reboot. If set, acpi will attempt tonjl2006-07-292-2/+7
| | | | | | | | perform the reboot action via the reset register instead of our legacy method. Default is 0 (use legacy). This is needed because some systems hang on reboot even though they claim to support the reset register. MFC after: 2 days
* Add /usr/lib/engines for OpenSSL engines.simon2006-07-292-0/+4
|
* Bump __FreeBSD_version for OpenSSL 0.9.8b import.simon2006-07-291-1/+1
|
* Link kldxref(8) static on PowerPC to work around a SIGSEGV thatmarcel2006-07-291-0/+4
| | | | | | | cannot easily be analyzed due to there being no debugger yet. The SIGSEGV only happens when kldxref is linked shared. Since kldxref(8) is needed for a release build, having it not dump core is important.
* Upgrade to OpenSSL 0.9.8b.simon2006-07-29299-3674/+6561
|
* Change maketempfile() to return a FILE* so as to eliminate the fopen()marcel2006-07-291-6/+7
| | | | | | | | | | that immediately follows the only call to it. maketempfile() uses mkstemp(), so the temporary file has already been opened and using fopen() again just opens the file twice. This also fixes the invalid mode used on the fopen(). While here, assign NULL to fxref after fclose() because we test for fxref being !NULL to determine if we have the (temporary) hints file open.
* Resolve conflicts after import of OpenSSL 0.9.8b.simon2006-07-29112-24404/+1759
|
* This commit was generated by cvs2svn to compensate for changes in r160814,simon2006-07-29892-19778/+97022
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Vendor import of OpenSSL 0.9.8bsimon2006-07-29915-20663/+98999
| |
| * Remove files that are no longer part of OpenSSL from the vendornectar2005-02-2557-15302/+0
| | | | | | | | branch. This time, these are mostly the `Makefile.ssl' files.
* | Remove sio(4) and related options from MI files to amd64, i386marcel2006-07-2915-44/+141
| | | | | | | | | | | | | | | | | | and pc98 MD files. Remove nodevice and nooption lines specific to sio(4) from ia64, powerpc and sparc64 NOTES. There were no such lines for arm yet. sio(4) is usable on less than half the platforms, not counting a future mips platform. Its presence in MI files is therefore increasingly becoming a burden.
* | Tell more of the sh(1) history.yar2006-07-291-2/+17
| | | | | | | | | | | | Acknowledge Kenneth Almquist's contribution in AUTHORS. MFC after: 5 days
OpenPOWER on IntegriCloud