Give every thread its own RNG state so there's no competition for the
cache lines.
Initialize the random-number generator early so we catch all possible
configuration uses.
Remove duplicates of WiredTiger's macros.
Break hardware.h up into gcc.h and lint.h (hardware.h is still there,
but it's mostly empty).
Remove need for gcc.h from various benchmarking/test programs.
row-store cursor code, but completely broken column-store cursors (I
haven't done any work on them yet). I'm about to try and re-work the
general-purpose walk code, and I want to have a solid reference point
to revert to. Here's the laundry list:
Re-write the row-store cursor-next/cursor-prev functions to interact
cleanly with the other cursor functions, specifically after any cursor
operation returns successfully, a subsequent cursor-next/prev call is
supported. The fundamental trick here is choosing the fields that a
cursor-search call sets, and then filling in the rest of the fields a
traversal requires as soon as cursor-next/prev is called. The state of
a cursor is set in the WT_CURSOR_BTREE->iter_state field. There's a new
"walk" function that fills in the walk stack from the root to a
specified page. As part of this, the SESSION.srch structure will go
away, replaced by the WT_CURSOR_BTREE structure.
Implement cursor semantics for row-store: update fails if the key
doesn't exist, otherwise overwrites the value; insert fails if the key
exists, otherwise inserts a new record, unless the configuration boolean
"overwrite" is set, in which case insert inserts a new record if the
record doesn't exist, and overwrites any existing record; remove fails
if the key doesn't exist, otherwise removes the record. Fail in all
cases if the application hasn't yet set a cursor key.
Flush memory after reading the page's write-generation value to ensure
that we do the read before reading anything from the page. This is
necessary but not sufficient: the page's write-generation value could
still be cache, and that would be bad. We need to either do an
additional memory flush before the read, in order to flush our
registers, or mark the write-generation field volatile.
Cursors now hold hazard references across calls (the page cannot be
discarded if a cursor references it). This is necessary for the future
change where cursor will return pointers to in-memory page data.
The __wt_walk_first/__wt_walk_last functions no longer support starting
at a random page, no current callers of those functions used that
feature.
Write versions of the serial insert/update functions that don't take
SESSION.srch pointers, instead, they pass the specific fields they need,
in some cases taken from the WT_CURSOR_BTREE structure.
Write a version of the return-value function to use information from the
WT_CURSOR_BTREE structure instead of information from the SESSION.srch
structure.
Delete the WT_CURSOR structure WT_CURSTD_POSITIONED flag (never used),
add the WT_CURSTD_OVERWRITE flag to support the cursor->insert boolean
"overwrite".
Delete the WT_TOOSMALL error, no longer used by compression.
Add support to the format test program to test prev/next cursor
movements after operations.
Configure the format test program to configure the boolean "overwrite"
value on its cursors, that matches the old BDB DB.put semantics the test
program wants.
Change the format test program to close its cursor before calling
WT_SESSION.sync, now that cursors hold hazard references across calls,
WT_SESSION.sync will hang.
Add statistics to track read-next/read-prev calls, separate from read
(search-near) calls.
--HG--
extra : rebase_source : a7b386152cef2a2744df26121b06536e7066fc95
