From: Matthew Wilcox <willy@infradead.org>
To: Nicolas Saenz Julienne <nsaenzju@redhat.com>
Cc: rostedt@goodmis.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com, corbet@lwn.net,
mtosatti@redhat.com
Subject: Re: [RFC] trace: Add option for polling ring buffers
Date: Wed, 19 May 2021 19:07:54 +0100 [thread overview]
Message-ID: <YKVT+sQTgNpCR/Gt@casper.infradead.org> (raw)
In-Reply-To: <20210519175755.670876-1-nsaenzju@redhat.com>
On Wed, May 19, 2021 at 07:57:55PM +0200, Nicolas Saenz Julienne wrote:
> To minimize trace's effect on isolated CPUs. That is, CPUs were only a
> handful or a single, process are allowed to run. Introduce a new trace
> option: 'poll-rb'.
maybe this should take a parameter in ms (us?) saying how frequently
to poll? it seems like a reasonable assumption that somebody running in
this kind of RT environment would be able to judge how often their
monitoring task needs to collect data.
> [1] The IPI, in this case, an irq_work, is needed since trace might run
> in NMI context. Which is not suitable for wake-ups.
could we also consider a try-wakeup which would not succeed if in NMI
context? or are there situations where we only gather data in NMI
context, and so would never succeed in waking up? if so, maybe
schedule the irq_work every 1000 failures to wake up.
next prev parent reply other threads:[~2021-05-19 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:57 Nicolas Saenz Julienne
2021-05-19 18:07 ` Matthew Wilcox [this message]
2021-05-19 19:33 ` Marcelo Tosatti
2021-05-20 8:57 ` Nicolas Saenz Julienne
2021-05-28 17:32 ` Steven Rostedt
2021-06-02 9:38 ` Nicolas Saenz Julienne
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=YKVT+sQTgNpCR/Gt@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®