From: Coly Li <colyli@suse.de>
To: Pony Cheng <ponycheng0@gmail.com>, linux-bcache@vger.kernel.org
Subject: Re: how to understand bcache
Date: Wed, 24 Jan 2018 17:10:41 +0800 [thread overview]
Message-ID: <7505a91a-e89b-af7e-9e1c-23632a4734e8@suse.de> (raw)
In-Reply-To: <CAATtUK=ABex5gos2LHdac+QiQbAP5HOmhrjCYez1wdQM5D7Z5A@mail.gmail.com>
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
next prev parent reply other threads:[~2018-01-24 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 2:34 how to understand bcache Pony Cheng
2018-01-24 9:10 ` Coly Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-24 9:34 tang.junhui
2018-01-25 1:54 ` Pony Cheng
2018-01-26 5:52 ` Michael Lyle
2018-01-26 6:27 tang.junhui
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=7505a91a-e89b-af7e-9e1c-23632a4734e8@suse.de \
--to=colyli@suse.de \
--cc=linux-bcache@vger.kernel.org \
--cc=ponycheng0@gmail.com \
/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).