All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Adams <jwadams@google.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	Jim Mattson <jmattson@google.com>,
	David Rientjes <rientjes@google.com>
Subject: Re: [RFC PATCH 0/7] metricfs metric file system and examples
Date: Fri, 7 Aug 2020 10:10:43 -0700	[thread overview]
Message-ID: <5de55a11-c08b-0a55-a678-4bf0d2266a83@infradead.org> (raw)
In-Reply-To: <20200806001431.2072150-1-jwadams@google.com>

On 8/5/20 5:14 PM, Jonathan Adams wrote:
> To try to restart the discussion of kernel statistics started by the
> statsfs patchsets (https://lkml.org/lkml/2020/5/26/332), I wanted
> to share the following set of patches which are Google's 'metricfs'
> implementation and some example uses.  Google has been using metricfs
> internally since 2012 as a way to export various statistics to our
> telemetry systems (similar to OpenTelemetry), and we have over 200
> statistics exported on a typical machine.
> 

Hi,

AFAIK all Linux filesystems (including pseudo/synthetic ones)
live under fs/, not in kernel/.

Therefore I think that this patch series needs more exposure,
i.e., Cc: it to linux-fsdevel@vger.kernel.org and netdev@vger.kernel.org.
oh, and to gregkh.


> Jonathan Adams (5):
>   core/metricfs: add support for percpu metricfs files
>   core/metricfs: metric for kernel warnings
>   core/metricfs: expose softirq information through metricfs
>   core/metricfs: expose scheduler stat information through metricfs
>   core/metricfs: expose x86-specific irq information through metricfs
> 
> Justin TerAvest (1):
>   core/metricfs: Create metricfs, standardized files under debugfs.
> 
> Laurent Chavey (1):
>   net-metricfs: Export /proc/net/dev via metricfs.
> 
>  arch/x86/kernel/irq.c      |  80 ++++
>  fs/proc/stat.c             |  57 +++
>  include/linux/metricfs.h   | 131 +++++++
>  kernel/Makefile            |   2 +
>  kernel/metricfs.c          | 775 +++++++++++++++++++++++++++++++++++++
>  kernel/metricfs_examples.c | 151 ++++++++
>  kernel/panic.c             | 131 +++++++
>  kernel/softirq.c           |  45 +++
>  lib/Kconfig.debug          |  18 +
>  net/core/Makefile          |   1 +
>  net/core/net_metricfs.c    | 194 ++++++++++
>  11 files changed, 1585 insertions(+)
>  create mode 100644 include/linux/metricfs.h
>  create mode 100644 kernel/metricfs.c
>  create mode 100644 kernel/metricfs_examples.c
>  create mode 100644 net/core/net_metricfs.c


thanks.
-- 
~Randy


  parent reply	other threads:[~2020-08-07 17:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  0:14 [RFC PATCH 0/7] metricfs metric file system and examples Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 1/7] core/metricfs: Create metricfs, standardized files under debugfs Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 2/7] core/metricfs: add support for percpu metricfs files Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 3/7] core/metricfs: metric for kernel warnings Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 4/7] core/metricfs: expose softirq information through metricfs Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 5/7] core/metricfs: expose scheduler stat " Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 6/7] core/metricfs: expose x86-specific irq " Jonathan Adams
2020-08-06  0:14 ` [RFC PATCH 7/7] net-metricfs: Export /proc/net/dev via metricfs Jonathan Adams
2020-08-07 17:10 ` Randy Dunlap [this message]
2020-08-07 21:29 [RFC PATCH 0/7] metricfs metric file system and examples Jonathan Adams
2020-08-08  2:06 ` Andrew Lunn
2020-08-08 15:59   ` David Ahern
2020-08-10 18:20     ` Jakub Kicinski
2020-08-10  9:23 ` Pavel Machek
2020-08-30 19:51 ` Steve French
2020-08-31  0:25   ` Tom Talpey
2020-08-31 21:25     ` Steve French
2020-09-01 13:04       ` Tom Talpey
2020-09-01 14:17         ` Chuck Lever

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=5de55a11-c08b-0a55-a678-4bf0d2266a83@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=jmattson@google.com \
    --cc=jwadams@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.