From: Jason Warr <jason-/cow75dQlsI@public.gmane.org>
To: Kent Overstreet <koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: block activity stats
Date: Tue, 30 Apr 2013 20:10:04 -0500 [thread overview]
Message-ID: <51806B6C.5060402@warr.net> (raw)
In-Reply-To: <20130430203134.GI9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Hi Kent,
I'm sort of using this thread as a point to jump into one thing I am
working on.
I am working on a munin plugin and configuration settings to track the
cache and backing device statistics. What metrics do you feel are
important to track for both the cache and backer? Sysstat will
obviously capture all of the raw device I/O numbers we would need but to
tell the whole picture I'm sure there are allot of stats bcache tracks
that would be nice to relate to the raw I/O.
I also plan to write a script that will output raw numbers in a similar
fashion to what you'd get with iostat so one can get more of a immediate
snapshot with definable intervals.
Thanks,
Jason
On 04/30/2013 03:31 PM, Kent Overstreet wrote:
> On Mon, Apr 29, 2013 at 08:46:50PM -0700, matthew patton wrote:
>> Is block activity tracked exclusively by Bcache code or is Bcache
>> piggy-backing on already existing statistics tracking that is
>> implemented in LVM or the VM or (scsi?) block layers? If the first, I
>> was wondering how hard it would be to move it into the lower levels
>> and turned on/off with sysfs.
>
> What sort of activity? Do you mean which blocks are cached and which
> aren't?
>
> That sort of thing is tracked entirely within bcache.
>
> Maybe you could tell me more specifically what you're trying to do?
>
>> Is there a whitepaper that goes into the mechanics of the tracking,
>> the granularity (eg. block region size), (de)promotion trigger logic,
>> etc? Or is this a question best answered by "go read the code"?
>
> There might be a more concise description of this stuff in the wiki, but
> probably the best documentation is going to be in the code - I wrote a
> lot of high level documentation and stuck it at the top of various
> files:
>
> http://atlas.evilpiepirate.org/git/linux-bcache.git/tree/drivers/md/bcache/bcache.h?h=bcache-dev
>
> http://atlas.evilpiepirate.org/git/linux-bcache.git/tree/drivers/md/bcache/alloc.c?h=bcache-dev
>
> http://atlas.evilpiepirate.org/git/linux-bcache.git/tree/drivers/md/bcache/btree.h?h=bcache-dev
>
> Let me know what's missing!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-05-01 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 15:43 Very poor performances with the bcache-for-upstream branch Leslie Basmid
[not found] ` <CA+XuAnJO4BCE0yj0i_CZ_iQvDj56FHwFZH302XrisD45P5R3Tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-29 17:52 ` Kent Overstreet
[not found] ` <CAC7rs0t4uKx37i7pxMoMQgVeUT6spDeridfdC+R6mqLbf1dwug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-30 3:46 ` block activity stats matthew patton
[not found] ` <1367293610.13617.YahooMailClassic-XYahOdtEMNn35Xbc4wGBzZOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-04-30 20:31 ` Kent Overstreet
[not found] ` <20130430203134.GI9931-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-05-01 1:10 ` Jason Warr [this message]
2013-05-01 13:30 ` Very poor performances with the bcache-for-upstream branch Leslie Basmid
[not found] ` <CA+XuAnK4nNOG_tSuuteDThbj5L+5xmDsxQLfrHj314z1fr+bUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-01 15:36 ` matthew patton
[not found] ` <1367422594.24900.YahooMailClassic-XYahOdtEMNm2Y7dhQGSVAJOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-05-01 16:56 ` Leslie Basmid
[not found] ` <CA+XuAn+Z-gxkfeE8D-A1-EJ4_QEBUqPJYfc40jevkJFbMzQ+Rw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-01 18:56 ` Kent Overstreet
[not found] ` <20130501185638.GB4057-jC9Py7bek1znysI04z7BkA@public.gmane.org>
2013-05-01 19:50 ` Leslie Basmid
2013-05-02 5:50 ` Gabriel de Perthuis
2013-05-02 16:13 ` Leslie Basmid
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=51806B6C.5060402@warr.net \
--to=jason-/cow75dqlsi@public.gmane.org \
--cc=koverstreet-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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