hi Tommi, Thanks for your reply. i am sorry for bothering you frequently. i see there are several daemons to handle the requests. i.e. client to osd, can you tell me what exactly source file will handle write/read request from client to/from osd? i am not clear with the structure of the source codes.
Thanks, Sheng On Mon, Oct 31, 2011 at 5:43 PM, Tommi Virtanen <[email protected]> wrote: > On Mon, Oct 31, 2011 at 15:27, sheng qiu <[email protected]> wrote: >> Thanks a lot for your help. >> i am trying to read the codes of ceph and get a deep understand of how >> it works with its components. but i find it very hard to get into it, >> can you give me some hint on how to read the codes efficiently? > > I'm afraid it comes down to reading, trying, failing, re-reading, and > repeating that a lot. > > I wrote a "big picture" overview of the architecture of Ceph (while > still trying to keep it very very short) over here: > http://ceph.newdream.net/docs/latest/architecture/ > > For me personally, knowledge of other network/distributed filesystems, > including things like HDFS, was pretty helpful in getting a grasp of > what's where. I still don't know much of the details of the messaging > etc, but I think one can get a good overview understanding of Ceph's > internals in a few weeks. > > I'm personally putting my time into making Ceph conceptually simpler, > not toward trying to explain the complexities. Hopefully that'll be > more useful, in the long run. > -- Sheng Qiu Texas A & M University Room 302 Wisenbaker email: [email protected] College Station, TX 77843-3259 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
