From: Andrew Morton <akpm@linux-foundation.org>
To: Tomas Mudrunka <tomas.mudrunka@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, rppt@kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net
Subject: Re: [PATCH v2] Add results of early memtest to /proc/meminfo
Date: Tue, 21 Mar 2023 13:01:55 -0700 [thread overview]
Message-ID: <20230321130155.dfd4ba94d093faa90213182b@linux-foundation.org> (raw)
In-Reply-To: <20230321103430.7130-1-tomas.mudrunka@gmail.com>
On Tue, 21 Mar 2023 11:34:30 +0100 Tomas Mudrunka <tomas.mudrunka@gmail.com> wrote:
> Currently the memtest results were only presented in dmesg.
> This adds /proc/meminfo entry which can be easily used by scripts.
Looks good to me, thanks. But the changelog still doesn't explain why
we should make this change. I grabbed that from your other email and
used the below as the changelog:
: Currently the memtest results were only presented in dmesg.
:
: When running a large fleet of devices without ECC RAM it's currently not
: easy to do bulk monitoring for memory corruption. You have to parse
: dmesg, but that's a ring buffer so the error might disappear after some
: time. In general I do not consider dmesg to be a great API to query RAM
: status.
:
: In several companies I've seen such errors remain undetected and cause
: issues for way too long. So I think it makes sense to provide a monitoring
: API, so that we can safely detect and act upon them.
:
: This adds /proc/meminfo entry which can be easily used by scripts.
next prev parent reply other threads:[~2023-03-21 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 19:30 [PATCH] Add results of early memtest to /proc/meminfo Tomáš Mudruňka
2023-03-17 23:56 ` Andrew Morton
2023-03-21 10:34 ` [PATCH v2] " Tomas Mudrunka
2023-03-21 20:01 ` Andrew Morton [this message]
2023-03-21 10:58 ` Re: [PATCH] " Tomas Mudrunka
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=20230321130155.dfd4ba94d093faa90213182b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=tomas.mudrunka@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).