libfoedus-core
FOEDUS Core Library
Public Member Functions | Public Attributes | List of all members
foedus::storage::StorageManagerControlBlock Struct Reference

Shared data in StorageManagerPimpl. More...

Detailed Description

Shared data in StorageManagerPimpl.

Definition at line 40 of file storage_manager_pimpl.hpp.

#include <storage_manager_pimpl.hpp>

Collaboration diagram for foedus::storage::StorageManagerControlBlock:
Collaboration graph
[legend]

Public Member Functions

 StorageManagerControlBlock ()=delete
 
 ~StorageManagerControlBlock ()=delete
 
void initialize ()
 
void uninitialize ()
 

Public Attributes

soc::SharedMutex mod_lock_
 In case there are multiple threads that add/delete/expand storages, those threads take this lock. More...
 
StorageId largest_storage_id_
 The largest StorageId we so far observed. More...
 

Constructor & Destructor Documentation

foedus::storage::StorageManagerControlBlock::StorageManagerControlBlock ( )
delete
foedus::storage::StorageManagerControlBlock::~StorageManagerControlBlock ( )
delete

Member Function Documentation

void foedus::storage::StorageManagerControlBlock::initialize ( )
inline

Definition at line 45 of file storage_manager_pimpl.hpp.

References foedus::soc::SharedMutex::initialize(), and mod_lock_.

Referenced by foedus::storage::StorageManagerPimpl::initialize_once().

45  {
46  mod_lock_.initialize();
47  }
foedus::soc::SharedMutex::initialize
void initialize(bool recursive=false)
Definition: shared_mutex.cpp:29
foedus::storage::StorageManagerControlBlock::mod_lock_
soc::SharedMutex mod_lock_
In case there are multiple threads that add/delete/expand storages, those threads take this lock...
Definition: storage_manager_pimpl.hpp:57

Here is the call graph for this function:

Here is the caller graph for this function:

void foedus::storage::StorageManagerControlBlock::uninitialize ( )
inline

Definition at line 48 of file storage_manager_pimpl.hpp.

References mod_lock_, and foedus::soc::SharedMutex::uninitialize().

Referenced by foedus::storage::StorageManagerPimpl::uninitialize_once().

48  {
49  mod_lock_.uninitialize();
50  }
foedus::storage::StorageManagerControlBlock::mod_lock_
soc::SharedMutex mod_lock_
In case there are multiple threads that add/delete/expand storages, those threads take this lock...
Definition: storage_manager_pimpl.hpp:57

Here is the call graph for this function:

Here is the caller graph for this function:

Member Data Documentation

StorageId foedus::storage::StorageManagerControlBlock::largest_storage_id_

The largest StorageId we so far observed.

This value +1 would be the ID of the storage created next.

Definition at line 63 of file storage_manager_pimpl.hpp.

Referenced by foedus::storage::StorageManagerPimpl::create_storage_apply(), foedus::storage::StorageManagerPimpl::exists(), foedus::storage::StorageManager::get_largest_storage_id(), foedus::storage::StorageManagerPimpl::get_storage(), foedus::storage::StorageManagerPimpl::initialize_once(), foedus::storage::StorageManagerPimpl::initialize_read_latest_snapshot(), foedus::storage::StorageManagerPimpl::issue_next_storage_id(), foedus::storage::StorageManagerPimpl::reinitialize_for_recovered_snapshot(), and foedus::storage::StorageManagerPimpl::uninitialize_once().

soc::SharedMutex foedus::storage::StorageManagerControlBlock::mod_lock_

In case there are multiple threads that add/delete/expand storages, those threads take this lock.

Normal threads that only read storages_ don't have to take this.

Definition at line 57 of file storage_manager_pimpl.hpp.

Referenced by foedus::storage::StorageManagerPimpl::exists(), foedus::storage::StorageManagerPimpl::get_storage(), initialize(), foedus::storage::StorageManagerPimpl::issue_next_storage_id(), and uninitialize().

The documentation for this struct was generated from the following file: