Re: Is there any way to collect object-level I/O access traces in Ceph?

2015-01-16 Thread Lipeng Wan
word I can search in the log file to locate the object operations? Thanks! LW On Fri, Jan 16, 2015 at 4:21 PM, Gregory Farnum wrote: > On Fri, Jan 16, 2015 at 11:28 AM, Lipeng Wan wrote: >> Dear all, >> >> Does Ceph provide a way to collect object-level I/O access traces? >

Is there any way to collect object-level I/O access traces in Ceph?

2015-01-16 Thread Lipeng Wan
Dear all, Does Ceph provide a way to collect object-level I/O access traces? Specifically, can we collect the traces to record how many times each object has been accessed (read, write, etc.) during a fixed period of time? Thanks! LW -- To unsubscribe from this list: send the line "unsubscribe ce

Question about the test() function in CrushTester class

2014-01-10 Thread Lipeng Wan
Hi guys, I am now trying to use crushtool.cc to test crush algorithm. First, I build a new crush map using crushtool.cc and all the devices have the maximum weight (0x1). Then I assign different weights to devices using the "--weight" option and run the test() function. It seems that during th

Re: question about the data structure of crush_map

2013-12-01 Thread Lipeng Wan
t; > On 2 December 2013 11:20, Lipeng Wan wrote: >> Hi guys, >> >> I am reading the source code of ceph and trying to understand the data >> structure of crush_map. Now I am confused by the use of "struct >> crush_bucket **buckets" in function "int cr

question about the data structure of crush_map

2013-12-01 Thread Lipeng Wan
Hi guys, I am reading the source code of ceph and trying to understand the data structure of crush_map. Now I am confused by the use of "struct crush_bucket **buckets" in function "int crush_do_rule(...)" in src/crush/mapper.c. It seems that the index of array "map->buckets[]" could be negative (s