Personally, I think it may be more important to improve portability of
Ceph at the architecture level. For example, the coming ARM64 support,
ARM has proven its name for its low power etc, it shoule be extremely
suitable for running IO extensive application like Ceph.
Does Inktank or any other
On 07/28/2013 02:35 AM, Li Wang wrote:
Personally, I think it may be more important to improve portability of
Ceph at the architecture level. For example, the coming ARM64 support,
ARM has proven its name for its low power etc, it shoule be extremely
suitable for running IO extensive application
On 24/07/2013 20:00, Loic Dachary wrote:
Hi,
Thanks for take the time to discuss LFS today @ OSCON :-) Would you be so kind
as to send links to the current discussion about the LFS driver API ?
Hi,
Here are some pointers to the LFS effort:
- Swift IRC meeting log:
On Sun, 28 Jul 2013, Li Wang wrote:
Personally, I think it may be more important to improve portability of Ceph at
the architecture level. For example, the coming ARM64 support,
ARM has proven its name for its low power etc, it shoule be extremely suitable
for running IO extensive application
ceph_build_auth() locks ac-mutex and then calls ceph_auth_build_hello()
that locks the same mutex, i.e. bring itself to deadlock.
The patch moves actual code from ceph_auth_build_hello() to
ceph_build_hello_auth_request() that should be called with ac-mutex held
and makes ceph_build_auth()
[snip]
I don't think the later was_short can handle the hole case. For the hole case,
we should try reading next strip object instead of return. how about
below patch.
Hi Yan,
i uesed this demo to test hole case.
dd if=/dev/urandom bs=4096 count=2 of=file_with_holes
dd if=/dev/urandom
One of the current problems with the ceph MDS is that the in-memory inode,
dentry, and dir structures (CInode, CDentry, CDir) are quite large. They
contain lots of fields for tracking the somewhat complicated lifecycle
that modified metadata takes before it is fully committed.
On Mon, Jul 29, 2013 at 11:00 AM, majianpeng majianp...@gmail.com wrote:
[snip]
I don't think the later was_short can handle the hole case. For the hole
case,
we should try reading next strip object instead of return. how about
below patch.
Hi Yan,
i uesed this demo to test hole