Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(761)

Unified Diff: net/disk_cache/blockfile/file_lock.h

Issue 992733002: Remove //net (except for Android test stuff) and sdch (Closed) Base URL: git@github.com:domokit/mojo.git@master
Patch Set: Created 5 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « net/disk_cache/blockfile/file_ios.cc ('k') | net/disk_cache/blockfile/file_lock.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: net/disk_cache/blockfile/file_lock.h
diff --git a/net/disk_cache/blockfile/file_lock.h b/net/disk_cache/blockfile/file_lock.h
deleted file mode 100644
index 3486aba18d19e15b6f01b3c9f174b852251ca6a7..0000000000000000000000000000000000000000
--- a/net/disk_cache/blockfile/file_lock.h
+++ /dev/null
@@ -1,45 +0,0 @@
-// Copyright (c) 2011 The Chromium Authors. All rights reserved.
-// Use of this source code is governed by a BSD-style license that can be
-// found in the LICENSE file.
-
-// See net/disk_cache/disk_cache.h for the public interface of the cache.
-
-#ifndef NET_DISK_CACHE_BLOCKFILE_FILE_LOCK_H_
-#define NET_DISK_CACHE_BLOCKFILE_FILE_LOCK_H_
-
-#include "net/base/net_export.h"
-#include "net/disk_cache/blockfile/disk_format_base.h"
-
-namespace disk_cache {
-
-// This class implements a file lock that lives on the header of a memory mapped
-// file. This is NOT a thread related lock, it is a lock to detect corruption
-// of the file when the process crashes in the middle of an update.
-// The lock is acquired on the constructor and released on the destructor.
-// The typical use of the class is:
-// {
-// BlockFileHeader* header = GetFileHeader();
-// FileLock lock(header);
-// header->max_entries = num_entries;
-// // At this point the destructor is going to release the lock.
-// }
-// It is important to perform Lock() and Unlock() operations in the right order,
-// because otherwise the desired effect of the "lock" will not be achieved. If
-// the operations are inlined / optimized, the "locked" operations can happen
-// outside the lock.
-class NET_EXPORT_PRIVATE FileLock {
- public:
- explicit FileLock(BlockFileHeader* header);
- virtual ~FileLock();
-
- // Virtual to make sure the compiler never inlines the calls.
- virtual void Lock();
- virtual void Unlock();
- private:
- bool acquired_;
- volatile int32* updating_;
-};
-
-} // namespace disk_cache
-
-#endif // NET_DISK_CACHE_BLOCKFILE_FILE_LOCK_H_
« no previous file with comments | « net/disk_cache/blockfile/file_ios.cc ('k') | net/disk_cache/blockfile/file_lock.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698