Clarify documentation for cache_pool size configuration.
Update wtperf to support insert threads in workload mode.
gcc knows __wt_abort() never returns, so it's complaining:
../src/support/err.c: In function ‘__wt_illegal_value’:
../src/support/err.c:395: warning: will never be executed
../src/support/err.c: In function ‘__wt_panic’:
../src/support/err.c:377: warning: will never be executed

Restructure the code slightly so it doesn't.
Now that __wt_cache_page_inmem_incr() does atomic updates, there's no
reason calling it needs to be inside the serialization function (and
probably good reason to move those calls outside of that function).
Also, __wt_cache_page_inmem_incr() is 3 atomic updates and we're
potentially calling it multiple times per serialization call: sum the
total memory we've "taken", and call it once.
If a page splits, it potentially creates a merge-split internal page and we
potentially walk that page during fast-delete.  The WT_REF.addr field doesn't
point to a cell in that case and we'll drop core.  This is the core Alex saw
when he ran test_truncate01 with his eviction of large pages changes.
Reference #418.
Rename __evict_list_clr_all to __evict_list_clr_range, it no longer clears
all the entries.
Update copyright notice to 2013.
Merge branch 'develop' into compact-in-thread