1 files changed, 0 insertions, 98 deletions
diff --git a/src/include/serial.i b/src/include/serial.i
deleted file mode 100644
index 0d04e1f716b..00000000000
--- a/src/include/serial.i
+++ /dev/null
@@ -1,98 +0,0 @@
-/*-
- * Copyright (c) 2008-2012 WiredTiger, Inc.
- *	All rights reserved.
- *
- * See the file LICENSE for redistribution information.
- */
-
-/*
- * Serialization: serialization support allows scheduling operations requiring
- * serialized access to a piece of memory, normally by a different thread of
- * control.  This includes updating and evicting pages from trees.
- *
- * __wt_session_serialize_func --
- *	Schedule a serialization request, and block or spin until it completes.
- */
-static inline int
-__wt_session_serialize_func(WT_SESSION_IMPL *session,
-    wq_state_t op, void (*func)(WT_SESSION_IMPL *), void *args)
-{
-	WT_CONNECTION_IMPL *conn;
-
-	conn = S2C(session);
-
-	/*
-	 * Threads serializing access to data using a function:
-	 *	call the function while holding a spinlock
-	 *	update the session sleeping state, and
-	 *	if necessary, block until an async action completes.
-	 */
-	session->wq_args = args;
-	session->wq_sleeping = (op == WT_SERIAL_EVICT);
-
-	/* Functions are serialized by holding a spinlock. */
-	__wt_spin_lock(session, &conn->serial_lock);
-
-	func(session);
-
-	__wt_spin_unlock(session, &conn->serial_lock);
-
-	switch (op) {
-	case WT_SERIAL_EVICT:
-		__wt_evict_server_wake(session);
-		break;
-	default:
-		break;
-	}
-
-	/*
-	 * If we are waiting on a server thread, block on the session condition
-	 * variable: when the operation is complete, this will be notified and
-	 * we can continue.
-	 */
-	if (session->wq_sleeping)
-		__wt_cond_wait(session, session->cond);
-	return (session->wq_ret);
-}
-
-/*
- * __wt_session_serialize_wrapup --
- *	Server function cleanup.
- */
-static inline void
-__wt_session_serialize_wrapup(WT_SESSION_IMPL *session, WT_PAGE *page, int ret)
-{
-	WT_BTREE *btree;
-
-	btree = session->btree;
-
-	/*
-	 * If passed a page and the return value is OK, we modified the tree
-	 * and the page.
-	 */
-	if (page != NULL && ret == 0) {
-		/*
-		 * A memory barrier is required for setting the tree's modified
-		 * value, we depend on the barrier called in setting the page's
-		 * modified value.
-		 */
-		btree->modified = 1;
-
-		__wt_page_modify_set(page);
-	}
-
-	/*
-	 * Publish: there must be a barrier to ensure the return value is set
-	 * before the calling thread can see its results, and the page's new
-	 * write generation makes it to memory.  The latter isn't a correctness
-	 * issue, the write generation just needs to be updated so that readers
-	 * get credit for reading the right version of the page, otherwise,
-	 * they will have to retry their update for reading an old version of
-	 * the page.
-	 */
-	WT_PUBLISH(session->wq_ret, ret);
-
-	/* If the calling thread is sleeping, wake it up. */
-	if (session->wq_sleeping)
-		__wt_cond_signal(session, session->cond);
-}