kernel - Improve VM fault performance for sequential access
authorMatthew Dillon <dillon@apollo.backplane.com>
Fri, 15 Jan 2010 03:40:14 +0000 (19:40 -0800)
committerMatthew Dillon <dillon@apollo.backplane.com>
Fri, 15 Jan 2010 03:44:29 +0000 (19:44 -0800)
commit768970b4fd5a55ad14ac037ab9bf530686f44db8
tree21b9e3f87826e5529a62c8cdfded7a1de2596981
parent959f863f59ab07a327558e1c1dc45c7dd6609d4f
kernel - Improve VM fault performance for sequential access

* VM fault I/O pipelining was not working properly.

* Temporarily fix pipelining by introducing PG_RAM, A read-ahead mark
  for vm_page_t, and adjust vm_fault to pass VM pages through to
  getpages calls if PG_RAM is set, even if they are fully valid.

* Remove code in vnode_pager_generic_getpages() which shortcutted
  the operation when the requested page was fully valid.  This
  prevented read-aheads from being issued.

* A more permanent solution is in the works (basically getting rid of
  the whole VM read-ahead/read-behind array entirely, just passing
  a single page through to vnode_pager_generic_getpages(), and
  letting the filesystem handle the read-ahead in a more efficient
  fashion.

Reported-by: "Mikhail T." <mi+thun@aldan.algebra.com>
sys/kern/vfs_cluster.c
sys/sys/vnode.h
sys/vm/vm_fault.c
sys/vm/vm_page.h
sys/vm/vnode_pager.c