summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* MFamd64/i386 r207205alc2010-04-301-13/+3
| | | | | | | | | | | | | | Clearing a page table entry's accessed bit and setting the page's PG_REFERENCED flag in pmap_protect() can't really be justified, so don't do it. Additionally, two changes that make this pmap behave like the others do: Change pmap_protect() such that it calls vm_page_dirty() only if the page is managed. Change pmap_remove_write() such that it doesn't clear a page table entry's accessed bit.
* Fix typo in usage message. Add -n to the list of valid arguments.philip2010-04-301-2/+2
| | | | MFC after: 1 day
* Revert r198705.mav2010-04-301-28/+1
| | | | | | | | | | | As scottl@ noticed, max_target/max_lun was intended to be only a hint for existing bus scanner. Some FC/SAS SIMs report fake values there, that are smaller then maximum supported IDs. In that case this check makes impossible manual scan outside hinted range. For ATA/SATA SIMs respective check was instead implemented at SIM level. Newer SCSI SIMs expected to have these checks at driver or firmware level. Some older SCSI SIMs have no this check and the issues will get back there.
* Add Target/LUN ID checks.mav2010-04-301-39/+26
|
* Add Target/LUN ID checks and deny access to targets 1-14 when PMP absent.mav2010-04-301-39/+28
|
* Add Target/LUN ID checks and deny access to targets 1-14 when PMP absent.mav2010-04-301-39/+30
| | | | Enforce PMA bit clearing when PMP detached to avoid further scan timeouts.
* Report PMP absence using target 15, same as for precence (not a wildcard),mav2010-04-301-4/+6
| | | | to not confuse target ID checks at SIMs.
* Fix improper pool write throughput calculation.mm2010-04-301-1/+1
| | | | | | | | | OpenSolaris onnv revision: 9366:17553395a745 PR: kern/146108 Approved by: pjd, delphij (mentor) Obtained from: OpenSolaris, Bug ID 6817339 MFC after: 2 weeks
* Avoid undefined behaviour.trasz2010-04-301-8/+11
| | | | Reviewed by: zec@
* - Use the path to the filesystem mountpoint to look up the statfsjeff2010-04-301-4/+4
| | | | | | | | structure so that we correctly reload. Note that tunefs doesn't properly detect the need to reload if the disk device is specified for a read-only mounted filesystem. - Lessen the contiguity requirement for the journal so that it is more likely to succeed.
* merge 194209 in to the i386/xen pmapkmacy2010-04-301-46/+47
| | | | requested by: alc@
* Avoid allocating MAXHOSTNAMELEN bytes on the stack in expand_name(),alfred2010-04-301-3/+19
| | | | | | | | use the heap instead. Obtained from: Juniper Networks Reviewed by: jhb
* Don't leak core_buf or gzfile if doing a compressed core file and wealfred2010-04-301-4/+7
| | | | | | hit an error condition. Obtained from: Juniper Networks
* Do not set IO_NODELOCKED while writing to vnodes as our consumersalfred2010-04-301-4/+4
| | | | | | | | do not lock the vnodes. Obtained from: Juniper Networks Reviewed by: jhb
* don't allow unsynchronized free in vm_page_unholdkmacy2010-04-301-1/+4
|
* - Enable flow control.davidch2010-04-302-791/+962
| | | | | | | | | | | | | | | - Print device details only when verbose boot is enabled. - Add debug output for shared memory access. - Add debug statistics (checksum offload & VLAN frame counters). - Modify TX path to update consumer index for each frame completed rather than updating the consumer index only once for a group of frames to improve small packet performance. - Print driver/firmware pulse messages only when verbose boot is enabled. - Add debug sysctl to clear statistics. - Fix more style(9) violations. MFC after: 2 weeks
* On Alan's advice, rather than do a wholesale conversion on a singlekmacy2010-04-3045-133/+587
| | | | | | | | | | | | architecture from page queue lock to a hashed array of page locks (based on a patch by Jeff Roberson), I've implemented page lock support in the MI code and have only moved vm_page's hold_count out from under page queue mutex to page lock. This changes pmap_extract_and_hold on all pmaps. Supported by: Bitgravity Inc. Discussed with: alc, jeffr, and kib
* Both RX_GMF_LP_THR and RX_GMF_UP_THR must be 16 bits register. Ifyongari2010-04-302-4/+4
| | | | | it is 8bits register then RX FIFO size can't exceed 2KB which is not true for almost all Yukon II controller.
* usb_controller.c requires opt_ddb.hthompsa2010-04-291-1/+1
|
* - Pass flow control settings back to bce(4).davidch2010-04-291-6/+4
| | | | MFC after: Two weeks
* Default connection timeout is way too long. To make it shorter we have topjd2010-04-291-3/+75
| | | | | | | | | make socket non-blocking, connect() and if we get EINPROGRESS, we have to wait using select(). Very complex, but I know no other way to define connection timeout for a given socket. Reported by: hiroshi@soupacific.com MFC after: 3 days
* Add FreeBSD 8.1 to known list as it's being referenced by a couple ofdelphij2010-04-291-0/+1
| | | | | | manpages already. MFC after: 3 days
* bwn(4) will first appear in FreeBSD 8.1-RELEASE.delphij2010-04-291-1/+1
| | | | MFC after: 1 week
* Now sge(4) supports hardware VLAN tag insertion/stripping.yongari2010-04-292-6/+6
|
* Enable VLAN hardware tag insertion/stripping. Due to lack of SiS190yongari2010-04-292-6/+60
| | | | | | | | | | | | | | controller, I'm not sure whether this is also applicable to SiS190 so this feature is only activated on SiS191 controller. In theory, controller reinitialization is not needed when VLAN tag configuration is changed, but xclin said controller was not stable whenever toggling VLAN tag bit. To address that, sge(4) reinitialize controller for VLAN configuration which seems to work as expected. VLAN tag information for TX/RX descriptor and configure bit of RxMacControl register was found by xclin. Submitted by: xclin <xclin <> cs dot nctu dot edu dot tw > (initial version) Tested by: xclin <xclin <> cs dot nctu dot edu dot tw >
* Enable FCS stripping and padding 10 bytes bit of RX MAC controlyongari2010-04-292-5/+32
| | | | | | | | | | | | | | | | | | | | register. Due to lack of SiS190 controller, I'm not sure whether this is also applicable to SiS190 so this feature is only activated on SiS191 controller. The controller can pad 10 bytes before DMAing a received frame to RX buffer and received bytes include the padded bytes. This padding is very useful on strict-alignment architectures because driver does not have to copy received frame to align IP header on 4 bytes boundary. It also gives better RX performance on non-strict alignment architectures. Special thanks to xclin to give me valuable register information. Without his enthusiastic trial and errors this wouldn't be even possible. While I'm here tighten validity check of received frame. Controller clears RDS_CRCOK bit when it received bad CRC frames. xclin found that using loop back testing. Tested by: xclin <xclin <> cs dot nctu dot edu dot tw >
* Explicitly marks SiS190 to differentiate it from SiS191.yongari2010-04-292-1/+2
|
* Remove wrong link state chage.yongari2010-04-291-1/+0
|
* Preserve unknown bits of RX MAC control register when driveryongari2010-04-291-15/+16
| | | | | | | | | programs RX filter configuration. It seems RX MAC control register is one of key registers to get various offloading features as well as performance. Blindly clearing unrelated bits can result in unexpected results. Tested by: xclin <xclin <> cs dot nctu dot edu dot tw >
* Simplify the inner loop of vm_pageout_object_deactivate_pages(). Ratheralc2010-04-291-7/+4
| | | | | | | | than checking each page for PG_UNMANAGED, check the vm object's type. Only OBJT_PHYS can have unmanaged pages. Eliminate a pointless counter. The vm object is locked, that lock is never released by the inner loop, and the set of pages contained by the vm object is not changed by the inner loop. Therefore, the counter serves no purpose.
* MFamd64/i386 r207205alc2010-04-293-28/+12
| | | | | | | Clearing a page table entry's accessed bit and setting the page's PG_REFERENCED flag in pmap_protect() can't really be justified, so don't do it. Moreover, on ia64, don't set the page's dirty field unless pmap_protect() is removing write access.
* - Check if the worker process was killed by signal and restart it.pjd2010-04-291-18/+26
| | | | | | | - Improve logging. Pointed out by: Garrett Cooper <yanefbsd@gmail.com> MFC after: 3 days
* Fix a problem where hastd will stuck in recv(2) after sending request topjd2010-04-2910-3/+87
| | | | | | | | | | secondary, which died between send(2) and recv(2). Do it by adding timeout to recv(2) for primary incoming and outgoing sockets and secondary outgoing socket. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> Tested by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Decrement rxa_pad due to the addition of rxa_private.rpaulo2010-04-291-1/+1
|
* MFP4: @176978-176982, 176984, 176990-176994, 177441bz2010-04-2952-682/+412
| | | | | | | | | | | | | | | | | | | | | | | | | | "Whitspace" churn after the VIMAGE/VNET whirls. Remove the need for some "init" functions within the network stack, like pim6_init(), icmp_init() or significantly shorten others like ip6_init() and nd6_init(), using static initialization again where possible and formerly missed. Move (most) variables back to the place they used to be before the container structs and VIMAGE_GLOABLS (before r185088) and try to reduce the diff to stable/7 and earlier as good as possible, to help out-of-tree consumers to update from 6.x or 7.x to 8 or 9. This also removes some header file pollution for putatively static global variables. Revert VIMAGE specific changes in ipfilter::ip_auth.c, that are no longer needed. Reviewed by: jhb Discussed with: rwatson Sponsored by: The FreeBSD Foundation Sponsored by: CK Software GmbH MFC after: 6 days
* ffs_vfsops: restore alphabetic order of options in ffs_optsavg2010-04-291-2/+2
| | | | | | | The order was not correct only for nfsv4acls. ("no" prefix is ignored) MFC after: 1 week
* When doing kstack swapin, read as much pages in one run as possible.kib2010-04-291-11/+25
| | | | | | Suggested and reviewed by: alc (previous version) Tested by: pho MFC after: 2 weeks
* In swap pager, do not free the non-requested pages from the run if they arekib2010-04-291-3/+11
| | | | | | | | | wired. Kstack pages are wired, this change prepares swap pager for handling of long runs of kstack pages. Noted and reviewed by: alc Tested by: pho MFC after: 2 weeks
* Remove caddr_t casts.kib2010-04-291-5/+3
| | | | | Requested by: bde MFC after: 10 days
* kern_ntptime: drop a comment that became stale after r207359avg2010-04-291-4/+0
| | | | | MFC after: 1 week X-MFC after: r207359
* periodically save system time to hardware time-of-day clockavg2010-04-291-0/+65
| | | | | | | | | | | | | | | This is done in kern_ntptime, perhaps not the best place. This is done using resettodr(). Some features: - make save period configurable via tunable and sysctl - period of zero disables saving, setting a non-zero period re-enables it or reschedules it - do saving only if system clock is ntp-synchronized - save on shutdown Discussed with: des, Peter Jeremy <peterjeremy@acm.org> X-Maybe: save time near seconds boundary for better precision MFC after: 2 weeks
* kern_ntptime: abstract time error check into a functionavg2010-04-291-23/+27
| | | | | | ... to avoid code duplication MFC after: 1 week
* MFi386: revision 206553nyan2010-04-291-4/+8
| | | | | - Change printf() calls to uprintf() for sigreturn(). - Normalize the messages to include both pid and thread name.
* On certain chipsets AT keyboard controller isn't present and issobomax2010-04-294-16/+69
| | | | | | | | | | | | | | | | | | | | emulated by BIOS using SMI interrupt. On those chipsets reading from the status port may be thousand times slower than usually. Sometimes this emilation is not working properly resulting in commands timing out and since we assume that inb() operation takes very little time to complete we need to adjust number of retries to keep waiting time within a designed limits (100ms). Measure time it takes to make read_status() call and adjust number of retries accordingly. To keep it simple, use TSC to measure inb() performance and keep it to amd64-only, since TSC may not available on older CPUs. Also enable detection of the AT controller absence on amd64. Reviewed by: jhb MFC after: 1 month
* For the experimental NFS client, it should always flush dirtyrmacklem2010-04-281-2/+1
| | | | | | | | | | buffers before closing the NFSv4 opens, as the comment states. This patch deletes the call to nfscl_mustflush() which would return 0 for the case where a delegation still exists, which was incorrect and could cause crashes during recovery from an expired lease. MFC after: 1 week
* Delete a diagnostic statement that is no longer useful fromrmacklem2010-04-281-4/+0
| | | | | | the experimental NFS client. MFC after: 1 week
* Restart worker thread only if the problem was temporary.pjd2010-04-281-3/+9
| | | | | | In case of persistent problem we don't want to loop forever. MFC after: 3 days
* Mark temporary issues as such.pjd2010-04-281-2/+2
| | | | MFC after: 3 days
* In the case where named_chroot_autoupdate is NOT set, butdougb2010-04-281-4/+10
| | | | | | | | | | | | | | | | named_chrootdir IS set, named-checkconf fails because it cannot find the conf file. Fix this by making checkconf a variable that includes "-t $named_chrootdir" as needed. Notice of the bug and suggested direction for the fix from [1]. Using required_files for named.conf is overkill ever since I added the named-checkconf call, so rather than update the logic to handle the case described above, remove it. This also handles the case where named_chroot_autoupdate IS set but the symlink doesn't exist yet. PR: conf/145904 Submitted by: J R Matthews
* Use WEXITSTATUS() to obtain real exit code.pjd2010-04-281-2/+3
| | | | MFC after: 3 days
OpenPOWER on IntegriCloud