FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2 2015-06-06T20:37:40Z 2015-06-06T20:37:40Z John Baldwin jhb@FreeBSD.org 2015-06-06T20:37:40Z urn:sha1:f0304fc03a37c215e38a4c2c1c9029e899c773da Place VM objects on the object list when created and never remove them. 261811: Fix function name in KASSERT(). 282660: Place VM objects on the object list when created and never remove them. This is ok since objects come from a NOFREE zone and allows objects to be locked while traversing the object list without triggering a LOR. Ensure that objects on the list are marked DEAD while free or stillborn, and that they have a refcount of zero. This required updating most of the pagers to explicitly mark an object as dead when deallocating it. (Only the vnode pager did this previously.) 282706: Satisfy vm_object uma zone destructor requirements after r282660 when vnode object creation raced. 2014-09-21T09:09:37Z Konstantin Belousov kib@FreeBSD.org 2014-09-21T09:09:37Z urn:sha1:37de92504c0a5498f389b2a6142070526c5fc5d6 Fix mis-spelling of bits and types names in the vnode_pager_putpages(). Approved by: re (delphij) 2013-08-09T11:11:11Z Attilio Rao attilio@FreeBSD.org 2013-08-09T11:11:11Z urn:sha1:c7aebda8a14a3bb94bb038df338549ccde5b56ea Unify the 2 concept into a real, minimal, sxlock where the shared acquisition represent the soft busy and the exclusive acquisition represent the hard busy. The old VPO_WANTED mechanism becames the hard-path for this new lock and it becomes per-page rather than per-object. The vm_object lock becames an interlock for this functionality: it can be held in both read or write mode. However, if the vm_object lock is held in read mode while acquiring or releasing the busy state, the thread owner cannot make any assumption on the busy state unless it is also busying it. Also: - Add a new flag to directly shared busy pages while vm_page_alloc and vm_page_grab are being executed. This will be very helpful once these functions happen under a read object lock. - Move the swapping sleep into its own per-object flag The KPI is heavilly changed this is why the version is bumped. It is very likely that some VM ports users will need to change their own code. Sponsored by: EMC / Isilon storage division Discussed with: alc Reviewed by: jeff, kib Tested by: gavin, bapt (older version) Tested by: pho, scottl 2013-07-23T22:52:38Z Jeff Roberson jeff@FreeBSD.org 2013-07-23T22:52:38Z urn:sha1:c93dcf2235b0cbc307458ee52b995cd989de6f44 done by vgonel() and destroy_vobject() should only be called once from VOP_INACTIVE(). Sponsored by: EMC / Isilon Storage Division 2013-04-28T19:19:26Z Konstantin Belousov kib@FreeBSD.org 2013-04-28T19:19:26Z urn:sha1:9b8851faae0dd4d42f422929b9377a4d1df0bcbf to vnode_pager_setsize(), is either OBJT_VNODE, or, if vnode was already reclaimed, OBJT_DEAD. Note that the later is only possible due to some filesystems, in particular, nfsiods from nfs clients, call vnode_pager_setsize() with unlocked vnode. More, if the object is terminated, do not perform the resizing operation. Reviewed by: alc Tested by: pho, bf MFC after: 1 week 2013-04-28T18:40:55Z Konstantin Belousov kib@FreeBSD.org 2013-04-28T18:40:55Z urn:sha1:6ded84276d6ed47bee7dbd0b9d2f0a3569d3e4f6 Reviewed by: alc MFC after: 1 week 2013-03-20T09:44:23Z Konstantin Belousov kib@FreeBSD.org 2013-03-20T09:44:23Z urn:sha1:6991ee13a69a7900f08776121a58d3bba813deee Noted by: mckay 2013-03-19T14:36:28Z Konstantin Belousov kib@FreeBSD.org 2013-03-19T14:36:28Z urn:sha1:6ce697dc73ef5e3d1147a52c97ab6404e03290ab for the unmapped i/o. Sponsored by: The FreeBSD Foundation Tested by: pho 2013-03-14T20:31:39Z Konstantin Belousov kib@FreeBSD.org 2013-03-14T20:31:39Z urn:sha1:70e198dd07ca521f10d74a285ac614e39648b16d Sponsored by: The FreeBSD Foundation 2013-03-09T02:32:23Z Attilio Rao attilio@FreeBSD.org 2013-03-09T02:32:23Z urn:sha1:89f6b8632cc94bca2738b4fcc26e1189ef4f5dde future further optimizations where the vm_object lock will be held in read mode most of the time the page cache resident pool of pages are accessed for reading purposes. The change is mostly mechanical but few notes are reported: * The KPI changes as follow: - VM_OBJECT_LOCK() -> VM_OBJECT_WLOCK() - VM_OBJECT_TRYLOCK() -> VM_OBJECT_TRYWLOCK() - VM_OBJECT_UNLOCK() -> VM_OBJECT_WUNLOCK() - VM_OBJECT_LOCK_ASSERT(MA_OWNED) -> VM_OBJECT_ASSERT_WLOCKED() (in order to avoid visibility of implementation details) - The read-mode operations are added: VM_OBJECT_RLOCK(), VM_OBJECT_TRYRLOCK(), VM_OBJECT_RUNLOCK(), VM_OBJECT_ASSERT_RLOCKED(), VM_OBJECT_ASSERT_LOCKED() * The vm/vm_pager.h namespace pollution avoidance (forcing requiring sys/mutex.h in consumers directly to cater its inlining functions using VM_OBJECT_LOCK()) imposes that all the vm/vm_pager.h consumers now must include also sys/rwlock.h. * zfs requires a quite convoluted fix to include FreeBSD rwlocks into the compat layer because the name clash between FreeBSD and solaris versions must be avoided. At this purpose zfs redefines the vm_object locking functions directly, isolating the FreeBSD components in specific compat stubs. The KPI results heavilly broken by this commit. Thirdy part ports must be updated accordingly (I can think off-hand of VirtualBox, for example). Sponsored by: EMC / Isilon storage division Reviewed by: jeff Reviewed by: pjd (ZFS specific review) Discussed with: alc Tested by: pho