From: Pony Cheng <ponycheng0@gmail.com>
To: tang.junhui@zte.com.cn
Cc: colyli@suse.de, Michael Lyle <mlyle@lyle.org>,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: how to understand bcache
Date: Thu, 25 Jan 2018 09:54:37 +0800 [thread overview]
Message-ID: <CAATtUKngr+iTUk4daERvbr0A5ryh3dgArhc7TGWJyBwbephBhg@mail.gmail.com> (raw)
In-Reply-To: <1516786455-29038-1-git-send-email-tang.junhui@zte.com.cn>
OK, Thank you very much.
2018-01-24 17:34 GMT+08:00 <tang.junhui@zte.com.cn>:
> From: Tang Junhui <tang.junhui@zte.com.cn>
>
>> On 24/01/2018 10:34 AM, Pony Cheng wrote:
>> > Hi all,
>> >
>> > I'm beginner of kernel module, and I'm reading bcache codebase now.
>> > But I'm very confused about many details, such as b+tree and io path.
>> >
>> > So, what should I do now, do you have some advices?
>>
>> Hi Pony,
>>
>> Read the code, through out your questions. If the question is
>> easy/simple, you may have response.
>>
>> Coly Li
>
> It sounds interesting, hahahaha~~
>
> you'd better to known how the data organized in disk,
> and what is bkey, bset, btree node, and what erver else,
> and think about deeply: If I am the author, how would I write
> the code, and read the currently code, to find wether it written
> as your thought, judge about is it your wrong or the author, Then
> you understood bcache, and bcache also understood you.
>
> you also can ask our dear maintainer Mike, who knows all about bcache,
> but sometiomes he is very busy, It is normally you would hear nothing
> from him for one weeks or two, sometimes maybe three, but never five,
> since the merge window comes.
>
> Thanks,
> Tang Junhui
>
next prev parent reply other threads:[~2018-01-25 1:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 9:34 how to understand bcache tang.junhui
2018-01-25 1:54 ` Pony Cheng [this message]
2018-01-26 5:52 ` Michael Lyle
-- strict thread matches above, loose matches on Subject: below --
2018-01-26 6:27 tang.junhui
2018-01-24 2:34 Pony Cheng
2018-01-24 9:10 ` Coly Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAATtUKngr+iTUk4daERvbr0A5ryh3dgArhc7TGWJyBwbephBhg@mail.gmail.com \
--to=ponycheng0@gmail.com \
--cc=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=tang.junhui@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).