From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jim Mattson <jmattson@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>,
David Rientjes <rientjes@google.com>,
Jonathan Adams <jwadams@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics
Date: Wed, 27 May 2020 17:00:41 +0200 [thread overview]
Message-ID: <b0d11337-3ea4-d874-6013-ff8c3e9d6f26@redhat.com> (raw)
In-Reply-To: <20200527133309.GC793752@lunn.ch>
On 27/05/20 15:33, Andrew Lunn wrote:
>> I don't really know a lot about the networking subsystem, and as it was
>> pointed out in another email on patch 7 by Andrew, networking needs to
>> atomically gather and display statistics in order to make them consistent,
>> and currently this is not supported by stats_fs but could be added in
>> future.
>
> Do you have any idea how you will support atomic access? It does not
> seem easy to implement in a filesystem based model.
Hi Andrew,
there are plans to support binary access. Emanuele and I don't really
have a plan for how to implement it, but there are developers from
Google that have ideas (because Google has a similar "metricfs" thing
in-house).
I think atomic access would use some kind of "source_ops" struct
containing create_snapshot and release_snapshot function pointers.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>,
linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
Jonathan Adams <jwadams@google.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Rientjes <rientjes@google.com>,
linux-fsdevel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics
Date: Wed, 27 May 2020 17:00:41 +0200 [thread overview]
Message-ID: <b0d11337-3ea4-d874-6013-ff8c3e9d6f26@redhat.com> (raw)
In-Reply-To: <20200527133309.GC793752@lunn.ch>
On 27/05/20 15:33, Andrew Lunn wrote:
>> I don't really know a lot about the networking subsystem, and as it was
>> pointed out in another email on patch 7 by Andrew, networking needs to
>> atomically gather and display statistics in order to make them consistent,
>> and currently this is not supported by stats_fs but could be added in
>> future.
>
> Do you have any idea how you will support atomic access? It does not
> seem easy to implement in a filesystem based model.
Hi Andrew,
there are plans to support binary access. Emanuele and I don't really
have a plan for how to implement it, but there are developers from
Google that have ideas (because Google has a similar "metricfs" thing
in-house).
I think atomic access would use some kind of "source_ops" struct
containing create_snapshot and release_snapshot function pointers.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>,
linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
Jonathan Adams <jwadams@google.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
David Rientjes <rientjes@google.com>,
linux-fsdevel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics
Date: Wed, 27 May 2020 17:00:41 +0200 [thread overview]
Message-ID: <b0d11337-3ea4-d874-6013-ff8c3e9d6f26@redhat.com> (raw)
In-Reply-To: <20200527133309.GC793752@lunn.ch>
On 27/05/20 15:33, Andrew Lunn wrote:
>> I don't really know a lot about the networking subsystem, and as it was
>> pointed out in another email on patch 7 by Andrew, networking needs to
>> atomically gather and display statistics in order to make them consistent,
>> and currently this is not supported by stats_fs but could be added in
>> future.
>
> Do you have any idea how you will support atomic access? It does not
> seem easy to implement in a filesystem based model.
Hi Andrew,
there are plans to support binary access. Emanuele and I don't really
have a plan for how to implement it, but there are developers from
Google that have ideas (because Google has a similar "metricfs" thing
in-house).
I think atomic access would use some kind of "source_ops" struct
containing create_snapshot and release_snapshot function pointers.
Paolo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jim Mattson <jmattson@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>,
David Rientjes <rientjes@google.com>,
Jonathan Adams <jwadams@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics
Date: Wed, 27 May 2020 15:00:41 +0000 [thread overview]
Message-ID: <b0d11337-3ea4-d874-6013-ff8c3e9d6f26@redhat.com> (raw)
In-Reply-To: <20200527133309.GC793752@lunn.ch>
On 27/05/20 15:33, Andrew Lunn wrote:
>> I don't really know a lot about the networking subsystem, and as it was
>> pointed out in another email on patch 7 by Andrew, networking needs to
>> atomically gather and display statistics in order to make them consistent,
>> and currently this is not supported by stats_fs but could be added in
>> future.
>
> Do you have any idea how you will support atomic access? It does not
> seem easy to implement in a filesystem based model.
Hi Andrew,
there are plans to support binary access. Emanuele and I don't really
have a plan for how to implement it, but there are developers from
Google that have ideas (because Google has a similar "metricfs" thing
in-house).
I think atomic access would use some kind of "source_ops" struct
containing create_snapshot and release_snapshot function pointers.
Paolo
next prev parent reply other threads:[~2020-05-27 15:00 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 11:03 [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 1/7] stats_fs API: create, add and remove stats_fs sources and values Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 2/7] documentation for stats_fs Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-06-04 0:23 ` Randy Dunlap
2020-06-04 0:23 ` Randy Dunlap
2020-06-04 0:23 ` Randy Dunlap
2020-06-04 0:23 ` Randy Dunlap
2020-06-04 15:34 ` Emanuele Giuseppe Esposito
2020-06-04 15:34 ` Emanuele Giuseppe Esposito
2020-06-04 15:34 ` Emanuele Giuseppe Esposito
2020-06-04 15:34 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 3/7] kunit: tests for stats_fs API Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-27 10:05 ` Alan Maguire
2020-05-27 10:05 ` Alan Maguire
2020-05-27 10:05 ` Alan Maguire
2020-05-27 10:05 ` Alan Maguire
2020-05-27 13:26 ` Emanuele Giuseppe Esposito
2020-05-27 13:26 ` Emanuele Giuseppe Esposito
2020-05-27 13:26 ` Emanuele Giuseppe Esposito
2020-05-27 13:26 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 4/7] stats_fs fs: virtual fs to show stats to the end-user Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 5/7] kvm_main: replace debugfs with stats_fs Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 6/7] [not for merge] kvm: example of stats_fs_value show function Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 7/7] [not for merge] netstats: example use of stats_fs API Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito
2020-05-26 14:16 ` Andrew Lunn
2020-05-26 14:16 ` Andrew Lunn
2020-05-26 14:16 ` Andrew Lunn
2020-05-26 14:16 ` Andrew Lunn
2020-05-26 15:45 ` Emanuele Giuseppe Esposito
2020-05-26 15:45 ` Emanuele Giuseppe Esposito
2020-05-26 15:45 ` Emanuele Giuseppe Esposito
2020-05-26 15:45 ` Emanuele Giuseppe Esposito
2020-05-26 22:31 ` [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics Jakub Kicinski
2020-05-26 22:31 ` Jakub Kicinski
2020-05-26 22:31 ` Jakub Kicinski
2020-05-26 22:31 ` Jakub Kicinski
2020-05-27 13:14 ` Emanuele Giuseppe Esposito
2020-05-27 13:14 ` Emanuele Giuseppe Esposito
2020-05-27 13:14 ` Emanuele Giuseppe Esposito
2020-05-27 13:14 ` Emanuele Giuseppe Esposito
2020-05-27 13:33 ` Andrew Lunn
2020-05-27 13:33 ` Andrew Lunn
2020-05-27 13:33 ` Andrew Lunn
2020-05-27 13:33 ` Andrew Lunn
2020-05-27 15:00 ` Paolo Bonzini [this message]
2020-05-27 15:00 ` Paolo Bonzini
2020-05-27 15:00 ` Paolo Bonzini
2020-05-27 15:00 ` Paolo Bonzini
2020-05-27 20:23 ` Jakub Kicinski
2020-05-27 20:23 ` Jakub Kicinski
2020-05-27 20:23 ` Jakub Kicinski
2020-05-27 20:23 ` Jakub Kicinski
2020-05-27 21:07 ` Paolo Bonzini
2020-05-27 21:07 ` Paolo Bonzini
2020-05-27 21:07 ` Paolo Bonzini
2020-05-27 21:07 ` Paolo Bonzini
2020-05-27 21:27 ` Jakub Kicinski
2020-05-27 21:27 ` Jakub Kicinski
2020-05-27 21:27 ` Jakub Kicinski
2020-05-27 21:27 ` Jakub Kicinski
2020-05-27 21:44 ` Paolo Bonzini
2020-05-27 21:44 ` Paolo Bonzini
2020-05-27 21:44 ` Paolo Bonzini
2020-05-27 21:44 ` Paolo Bonzini
2020-05-27 22:21 ` David Ahern
2020-05-27 22:21 ` David Ahern
2020-05-27 22:21 ` David Ahern
2020-05-27 22:21 ` David Ahern
2020-05-28 5:22 ` Paolo Bonzini
2020-05-28 5:22 ` Paolo Bonzini
2020-05-28 5:22 ` Paolo Bonzini
2020-05-28 5:22 ` Paolo Bonzini
2020-05-27 21:17 ` Andrew Lunn
2020-05-27 21:17 ` Andrew Lunn
2020-05-27 21:17 ` Andrew Lunn
2020-05-27 21:17 ` Andrew Lunn
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=b0d11337-3ea4-d874-6013-ff8c3e9d6f26@redhat.com \
--to=pbonzini@redhat.com \
--cc=andrew@lunn.ch \
--cc=borntraeger@de.ibm.com \
--cc=e.emanuelegiuseppe@gmail.com \
--cc=eesposit@redhat.com \
--cc=jmattson@google.com \
--cc=jwadams@google.com \
--cc=kuba@kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rientjes@google.com \
--cc=viro@zeniv.linux.org.uk \
/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.