summaryrefslogtreecommitdiffstats
path: root/sys/contrib/opensolaris/uts
Commit message (Collapse)AuthorAgeFilesLines
* Remove files that have been repo copied to their new locationjb2008-03-28176-80231/+0
| | | | in cddl-specific parts of the source tree.
* Add the new kernel-mode NFS Lock Manager. To use it instead of thedfr2008-03-261-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | user-mode lock manager, build a kernel with the NFSLOCKD option and add '-k' to 'rpc_lockd_flags' in rc.conf. Highlights include: * Thread-safe kernel RPC client - many threads can use the same RPC client handle safely with replies being de-multiplexed at the socket upcall (typically driven directly by the NIC interrupt) and handed off to whichever thread matches the reply. For UDP sockets, many RPC clients can share the same socket. This allows the use of a single privileged UDP port number to talk to an arbitrary number of remote hosts. * Single-threaded kernel RPC server. Adding support for multi-threaded server would be relatively straightforward and would follow approximately the Solaris KPI. A single thread should be sufficient for the NLM since it should rarely block in normal operation. * Kernel mode NLM server supporting cancel requests and granted callbacks. I've tested the NLM server reasonably extensively - it passes both my own tests and the NFS Connectathon locking tests running on Solaris, Mac OS X and Ubuntu Linux. * Userland NLM client supported. While the NLM server doesn't have support for the local NFS client's locking needs, it does have to field async replies and granted callbacks from remote NLMs that the local client has contacted. We relay these replies to the userland rpc.lockd over a local domain RPC socket. * Robust deadlock detection for the local lock manager. In particular it will detect deadlocks caused by a lock request that covers more than one blocking request. As required by the NLM protocol, all deadlock detection happens synchronously - a user is guaranteed that if a lock request isn't rejected immediately, the lock will eventually be granted. The old system allowed for a 'deferred deadlock' condition where a blocked lock request could wake up and find that some other deadlock-causing lock owner had beaten them to the lock. * Since both local and remote locks are managed by the same kernel locking code, local and remote processes can safely use file locks for mutual exclusion. Local processes have no fairness advantage compared to remote processes when contending to lock a region that has just been unlocked - the local lock manager enforces a strict first-come first-served model for both local and remote lockers. Sponsored by: Isilon Systems PR: 95247 107555 115524 116679 MFC after: 2 weeks
* In keeping with style(9)'s recommendations on macros, use a ';'rwatson2008-03-162-2/+2
| | | | | | | | | after each SYSINIT() macro invocation. This makes a number of lightweight C parsers much happier with the FreeBSD kernel source, including cflow's prcc and lxr. MFC after: 1 month Discussed with: imp, rink
* Fix mmap(2) on ZFS after some changes in VM subsystem.pjd2008-03-151-0/+4
| | | | | | | Submitted by: alc Reported by: kris (originally) and many others Tested with: fsx MFC after: 1 week
* Axe the 'thread' argument from VOP_ISLOCKED() and lockstatus() as it isattilio2008-02-251-3/+3
| | | | | | | | | always curthread. As KPI gets broken by this patch, manpages and __FreeBSD_version will be updated by further commits. Tested by: Andrea Barberio <insomniac at slackware dot it>
* Introduce some functions in the vnode locks namespace and in the ffsattilio2008-02-241-4/+4
| | | | | | | | | | | | | | | namespace in order to handle lockmgr fields in a controlled way instead than spreading all around bogus stubs: - VN_LOCK_AREC() allows lock recursion for a specified vnode - VN_LOCK_ASHARE() allows lock sharing for a specified vnode In FFS land: - BUF_AREC() allows lock recursion for a specified buffer lock - BUF_NOREC() disallows recursion for a specified buffer lock Side note: union_subr.c::unionfs_node_update() is the only other function directly handling lockmgr fields. As this is not simple to fix, it has been left behind as "sole" exception.
* - Reduce how much ZFS caches by default. This is another change to mitigatepjd2008-01-241-4/+5
| | | | | | | 'kmem_map too small panics'. - Print two warnings if there is not enough memory and not enough address space. - Improve comment.
* VOP_LOCK1() (and so VOP_LOCK()) and VOP_UNLOCK() are only used inattilio2008-01-134-14/+14
| | | | | | | | | | | conjuction with 'thread' argument passing which is always curthread. Remove the unuseful extra-argument and pass explicitly curthread to lower layer functions, when necessary. KPI results broken by this change, which should affect several ports, so version bumping and manpage update will be further committed. Tested by: kris, pho, Diego Sardina <siarodx at gmail dot com>
* vn_lock() is currently only used with the 'curthread' passed as argument.attilio2008-01-106-21/+21
| | | | | | | | | | | | | | | | Remove this argument and pass curthread directly to underlying VOP_LOCK1() VFS method. This modify makes the code cleaner and in particular remove an annoying dependence helping next lockmgr() cleanup. KPI results, obviously, changed. Manpage and FreeBSD_version will be updated through further commits. As a side note, would be valuable to say that next commits will address a similar cleanup about VFS methods, in particular vop_lock1 and vop_unlock. Tested by: Diego Sardina <siarodx at gmail dot com>, Andrea Di Pasquale <whyx dot it at gmail dot com>
* * Check endianness the FreeBSD way.jb2007-11-2812-30/+43
| | | | | * Use LBOLT rather than lbolt to avoid a clash with a FreeBSD global variable.
* Fix a prototype definition.jb2007-11-281-1/+1
|
* Warn if kmem_map size is set to less than 512MB. Previous warning was a bitpjd2007-11-071-5/+5
| | | | | | | pointless, because default is set to something around 300MB and also insufficient. MFC after: 3 days
* Remove unused header.pjd2007-11-051-569/+0
| | | | MFC after: 3 days
* If setting a state to anything but open state, close access to vdev.pjd2007-11-051-0/+11
| | | | | | | This fixes replacing drive in place, eg. zpool replace tank da1 da1. Before it complained that device is already open. MFC after: 1 week
* - Add sysctl for sizeof(znode_t), which will be used by fstat(1).lulf2007-11-021-0/+4
| | | | Approved by: pjd (mentor)
* Call zil_commit() (if ZIL is not disabled) after every non-read requestpjd2007-11-011-11/+11
| | | | | | | | (BIO_WRITE and BIO_FLUSH) as it is done is Solaris. The difference is that Solaris calls it only for sync requests, but we can't say in GEOM is the request is sync or async, so we do it for every request. MFC after: 1 week
* Rename the kthread_xxx (e.g. kthread_create()) callsjulian2007-10-202-4/+4
| | | | | | | | | | | to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first. I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
* ZFS_LOG adds a newline by itself.thompsa2007-10-141-1/+1
| | | | Pointed out by: pjd
* Print the ZFS ereport to the console if vfs.zfs.debug is set to help diagnosethompsa2007-10-141-0/+1
| | | | | | problems with zfs-on-root since devd isnt running yet. Reviewed by: pjd
* Fix lock leak leading to the 'System call <name> returning with 1 locks held'pjd2007-10-041-0/+2
| | | | | | | panic. Reported by: kris Approved by: re (kensmith)
* Reduce the limit of vnodes on i386 when ZFS is loaded to 3/4 of the originalpjd2007-09-101-0/+41
| | | | | | | | | | | | | value, so we don't run out of KVA. The default vnodes limit fits better for UFS, but ZFS allocated more file system specific memory for a vnode than UFS. Don't touch vnodes limit if we detect it was tuned by system administrator and restore original value when ZFS is unloaded. This isn't final fix, but before we implement something better, this will help to stabilize ZFS under heavy load on i386. Approved by: re (bmah)
* After dfr@ vnode leak fix, we can allow ARC to consume more memory.pjd2007-09-101-2/+2
| | | | | Tested by: kris Approved by: re (bmah)
* Use CTLFLAG_RDTUN for tunable sysctls.pjd2007-09-011-2/+2
| | | | Approved by: re (bmah)
* Update assertion after revision 1.23.pjd2007-07-241-1/+1
| | | | | Reviewed by: dfr Approved by: re (rwatson)
* Correct a reference-counting mistake in the ZFS code which led to abnormaldfr2007-07-092-3/+1
| | | | | | | memory usage and pessimal cache performance. Reviewed by: pjd Approved by: re (rwatson)
* In zfs_vget, if we fail to translate an inode number to the correspondingdfr2007-06-271-1/+1
| | | | | | | vnode, make sure we return an error code to the caller. Reviewed by: pjd Approved by: re
* - Reduce number of atomic operations needed to be implemented in asm bypjd2007-06-083-655/+27
| | | | | | | implementing some of them using existing ones. - Allow to compile ZFS on all archs and use atomic operations surrounded by global mutex on archs we don't have or can't have all atomic operations needed by ZFS.
* Reimplement traverse() helper function:pjd2007-06-041-10/+9
| | | | | | | | | | | | 1. Pass locking flags to VFS_ROOT(). 2. Check v_mountedhere while the vnode is locked. 3. Always return locked vnode on success. Change 1 fixes problem reported by Stephen M. Rumble - after zfs_vfsops.c,1.9 change, zfs_root() no longer locks the vnode unconditionally and traverse() didn't pass right lock type to VFS_ROOT(). The result was that kernel paniced when .zfs/ directory was accessed via NFS.
* Adjust va_mask for setattr. FreeBSD doesn't have va_mask, so we initialize itpjd2007-05-281-0/+1
| | | | | | | | based on individual fields beeing set. This doesn't work for setattr replay, because va_type is set there, so we add AT_TYPE flag to va_mask, which won't be accepted by zfs_setattr(). Reported by: kris
* Because we allocate componentname structures on stack, bzero() them beforepjd2007-05-281-0/+3
| | | | use just in case.
* Initialize ZFS a bit earlier and block root mounting untilpjd2007-05-241-1/+4
| | | | | | | | initialization is complete. This fixes some root-on-ZFS configurations. Reported by: Bruno Damour <freebsd.ruomad@free.fr> Tested by: Bruno Damour <freebsd.ruomad@free.fr>
* FreeBSD's namecache works quite well with ZFS, so remove DNLC.pjd2007-05-232-1075/+0
|
* All objects we create using GFS are directories, so initialize d_typepjd2007-05-231-2/+2
| | | | | properly, but add XXX comment saying that it can eventually change in the future.
* Lock vnode on lookup. This fixes ZIL replay for rmdir/unlink/rename.pjd2007-05-221-0/+3
| | | | Reported by: des
* Increase debug level - this message is not that important.pjd2007-05-091-1/+1
|
* - Add missing lock destruction and remove duplicate initializations.pjd2007-05-066-5/+14
| | | | | | With this change it is possible to unload zfs.ko module from WITNESS-enabled kernel. - Remove bogus comment.
* Use provider's ident to handle situations when disks are moved aroundpjd2007-05-061-10/+161
| | | | | | | and show up with different names: first try to open provider using remembered name and compare its ident, if equal, this is our provider, if not equal or there is no provider with such name, find provider with remembered ident and don't care about the name.
* MFp4: We don't need to cover vnode_pager_setsize() with the z_map_lock.pjd2007-05-061-1/+2
|
* Share-lock a vnode where possible.pjd2007-05-021-1/+1
|
* When parent directory has to be unlocked, lock it back with the same lockpjd2007-05-021-2/+6
| | | | | type. Before this change, if directory was shared-locked, it was relocked exclusively.
* Lock vnode using cn_lkflags in case the caller wants the vnode to bepjd2007-05-021-1/+1
| | | | shared-locked.
* The getnewvnode() function sets LK_NOSHARE by default, so if we want topjd2007-05-021-3/+9
| | | | | support shared vnodes locking, we need to remove that flag. Also add LK_CANRECURSE flag as found in nfsclient.
* ZFS should update timestamps upon the creat() of an existing file.pjd2007-05-022-2/+5
| | | | | Obtained from: OpenSolaris Bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6465105
* - Lock vnode with flags passed in as argument in zfs_vget() and zfs_root().pjd2007-05-021-2/+4
| | | | | | | Pointed out by: ups Also reported by: kris - Add comments where I'm not sure if LK_RETRY should be used.
* MFp4: Remove LK_RETRY flag when locking vnode in zfs_lookup, we don't wantpjd2007-05-011-1/+6
| | | | | | dead vnodes here. Suggested by: kib
* White space fixes.pjd2007-05-014-34/+34
|
* Add a comment explaining why we call dmu_write() unconditionally, even ifpjd2007-05-011-0/+9
| | | | | | | uiomove() fails, especially that it is different from what OpenSolaris does (I'm not entirely sure they are right). Suggested by: darrenr
* - Define d_type for ".", ".." and ".zfs" directories.pjd2007-04-292-0/+5
| | | | - Add a TODO comment where d_type is still noe defined.
* Oops, correct important typo in last commit.pjd2007-04-291-1/+1
|
* Avoid freeing NULL pointer in case of an error.pjd2007-04-291-1/+1
|
OpenPOWER on IntegriCloud