IndexManager now has a Index caching. Index will only be created if not found in the cache. Earlier, each op is creating an Index object and other ops requesting the same index needed to wait till previous op is done. Also, after finishing lookup, this Index object was destroyed. Now, a Index cache is been implemented to persists these Indexes since there is a major performance hit because each op is creating and destroying these. A RWlock is been introduced in the CollectionIndex class and that is responsible for sync between lookup and create. Also, since these Index objects are persistent there is no need to use smart pointers. So, Index is a wrapper class of CollecIndex* now. It is the responsibility of the users of Index now to lock explicitely before using them. Index object is sufficient now for locking and no need to hold IndexPath for locking. The function interfaces of lfn_open,lfn_find are changed accordingly. Signed-off-by: Somnath Roy <somnath.roy@sandisk.com> |
||
---|---|---|
admin | ||
ceph-object-corpus@bb3cee6b85 | ||
debian | ||
doc | ||
examples/librados | ||
fusetrace | ||
keys | ||
m4 | ||
man | ||
qa | ||
share | ||
src | ||
systemd | ||
udev | ||
wireshark | ||
.gitignore | ||
.gitmodule_mirrors | ||
.gitmodules | ||
.mailmap | ||
.organizationmap | ||
AUTHORS | ||
autogen.sh | ||
ceph.spec.in | ||
ChangeLog | ||
CodingStyle | ||
configure.ac | ||
COPYING | ||
COPYING-LGPL2.1 | ||
deps.deb.txt | ||
deps.rpm.txt | ||
do_autogen.sh | ||
doc_deps.deb.txt | ||
Doxyfile | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
PendingReleaseNotes | ||
README | ||
README.md | ||
SubmittingPatches |
============================================ Ceph - a scalable distributed storage system
Please see http://ceph.com/ for current info.
Contributing Code
Most of Ceph is licensed under the LGPL version 2.1. Some miscellaneous code is under BSD-style license or is public domain. The documentation is licensed under Creative Commons Attribution-ShareAlike (CC BY-SA). There are a handful of headers included here that are licensed under the GPL. Please see the file COPYING for a full inventory of licenses by file.
Code contributions must include a valid "Signed-off-by" acknowledging the license for the modified or contributed file. Please see the file SubmittingPatches for details on what that means and on how to generate and submit patches.
We do not require assignment of copyright to contribute code; code is contributed under the terms of the applicable license.
Build Prerequisites
debian-based
The list of debian package dependencies can be found in deps.deb.txt:
sudo apt-get install `cat deps.deb.txt`
Note: libsnappy-dev and libleveldb-dev are not available upstream for natty, oneiric, and squeeze. Backports for Ceph can be found at ceph.com/debian-leveldb.
rpm-based
The list of RPM package dependencies can be found in deps.rpm.txt:
sudo yum install `cat deps.rpm.txt`
Building Ceph
Developers, please refer to the Developer Guide for more information, otherwise, you can build the server daemons, and FUSE client, by executing the following:
./autogen.sh
./configure
make
(Note that the FUSE client will only be built if libfuse is present.)
Dependencies
The configure script will complain about any missing dependencies as it goes. You can also refer to debian/control or ceph.spec.in for the package build dependencies on those platforms. In many cases, dependencies can be avoided with --with-foo or --without-bar switches. For example,
./configure --with-nss # use libnss instead of libcrypto++
./configure --without-radosgw # do not build radosgw
./configure --without-tcmalloc # avoid google-perftools dependency
Building packages
You can build packages for Debian or Debian-derived (e.g., Ubuntu) systems with
sudo apt-get install dpkg-dev
dpkg-checkbuilddeps # make sure we have all dependencies
dpkg-buildpackage
For RPM-based systems (Red Hat, SUSE, etc.),
rpmbuild
Building the Documentation
Prerequisites
The list of package dependencies for building the documentation can be found in doc_deps.deb.txt:
sudo apt-get install `cat doc_deps.deb.txt`
Building the Documentation
To build the documentation, ensure that you are in the top-level `/ceph directory, and execute the build script. For example:
admin/build-doc