From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Ashley Herron <herroash@amazon.com>, <richard@nod.at>
Cc: <alex@nextthing.co>, <boris.brezillon@free-electrons.com>,
<linux-mtd@lists.infradead.org>, <rdlee@amazon.com>
Subject: Re: [RFC] UBI statistics and bitrot interface
Date: Sat, 15 Feb 2025 12:58:20 +0800 [thread overview]
Message-ID: <4e774297-22e6-d175-e46f-3806cf511f45@huawei.com> (raw)
In-Reply-To: <20250214160419.18583-1-herroash@amazon.com>
在 2025/2/15 0:04, Ashley Herron 写道:
>> IIRC, this patches have been part of our failed approach to support MLC
>> NAND. One part was exposing a more or less sophisticated interface
>> to userspace such that a NAND flash specific daemon can foster the chip.
>>
>>
>> After some iterations, ubihealthd was born. But it does not use a statistics
>> interface.
>
> Unfortunately ubihealthd wouldn't fit what we need.
>
>>
>> What kind of metrics are you looking for?
>> Maybe some eBPF/tracing magic will already serve you enough data points?
>
> The goal is to capture similar data as eMMC and UFS devices report regarding
> total bytes written to the block device. So I want to capture total (payload)
> bytes written by callers to the UBI layer, not including UBI overhead (headers,
> wear leveling). This is for the purpose of monitoring and identifying any
> pattern of excessive writing on devices in operation that may effect its
> lifetime.
> We may want to monitor total writes to a UBI device over a 24 hour
> periods or less, so only using erase counter monitoring doesn't give us the
> level of monitoring we require. We write to some UBI volumes using UBIFS
> and others using UBI IO directly. I was planning to add (or request you add) a
> wc (write count) variable to the current struct with ec and rc in this patchset.
>
I think ebpf/tracing will satisfy your requirements by hooking function
ubi_eba_write_leb().
> Cheers,
> Ashley
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
> .
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-02-15 4:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 22:56 [RFC] UBI statistics and bitrot interface Richard Weinberger
2015-11-05 22:56 ` [PATCH 1/5] UBI: Introduce prepare_erase_work() Richard Weinberger
2015-11-05 22:56 ` [PATCH 2/5] UBI: Introduce in_pq() Richard Weinberger
2015-11-05 22:56 ` [PATCH 3/5] UBI: Expose the bitrot interface Richard Weinberger
2015-11-06 11:59 ` Artem Bityutskiy
2015-11-06 12:14 ` Richard Weinberger
2015-11-06 12:30 ` Artem Bityutskiy
2015-11-06 12:27 ` Artem Bityutskiy
2015-11-05 22:56 ` [PATCH 4/5] UBI: Add basic read counter support Richard Weinberger
2015-11-05 22:56 ` [PATCH 5/5] UBI: Expose UBI statistics interface Richard Weinberger
2025-02-12 20:46 ` [RFC] UBI statistics and bitrot interface Ashley Herron
2025-02-12 21:58 ` Richard Weinberger
2025-02-14 16:04 ` Ashley Herron
2025-02-14 19:19 ` Richard Weinberger
2025-02-15 4:58 ` Zhihao Cheng [this message]
2025-02-15 5:21 ` Zhihao Cheng
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=4e774297-22e6-d175-e46f-3806cf511f45@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=alex@nextthing.co \
--cc=boris.brezillon@free-electrons.com \
--cc=herroash@amazon.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rdlee@amazon.com \
--cc=richard@nod.at \
/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).