From: Daniel Walter <dwalter@sigma-star.at>
To: linux-mtd@lists.infradead.org
Subject: [RFC] Trace-events for mtd
Date: Tue, 17 Nov 2015 20:14:48 +0100 [thread overview]
Message-ID: <20151117191448.GA5367@dw-nb.local> (raw)
Hi,
I currently working on ways to find out
if any processes are producing heavy I/O
loads on a mtd device.
I've implemented traceevents for mtd_read and
mtd_write which allow us to at least get a
rough overview on the read/write load.
Although it kinda works, I could not find a
way to find out which processes actually produce
write load, since all writes are writebacks from
page_cache and therefor we mostly get a kworker thread
as the main origin of any write load.
I wanted to reach out to the broader community to find
out if I missed somethings and to get overall feedback
if more traceevents would be useful to help us
debugging mtd i/o a little bit better.
any comments are highly appreciated.
Cheers,
daniel
next reply other threads:[~2015-11-17 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:14 Daniel Walter [this message]
2015-11-17 19:18 ` [RFC] [PATCH] mtd: add tracepoints for mtd_read and mtd_write Daniel Walter
2016-01-08 9:33 ` Richard Weinberger
2016-01-08 17:57 ` Brian Norris
2016-01-14 1:12 ` Daniel Walter
2016-01-08 18:00 ` [RFC] Trace-events for mtd Brian Norris
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=20151117191448.GA5367@dw-nb.local \
--to=dwalter@sigma-star.at \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).