From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
rjohnson@digitalocean.com,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH 1/2] tracing: show size of requested buffer
Date: Tue, 26 Oct 2021 17:26:37 -0400 [thread overview]
Message-ID: <20211026172637.65f576c3@gandalf.local.home> (raw)
In-Reply-To: <YXhx1N1/xe/v3wrI@hirez.programming.kicks-ass.net>
On Tue, 26 Oct 2021 23:23:32 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> > Do you have any real issue if I just take this patch set through my tree?
>
> No real objections; just weary, huge events like that are fairly sucky
> for performance.
OK. Then I'll just take this in, and let people have sucky performance if
they want huge events ;-)
-- Steve
next prev parent reply other threads:[~2021-10-26 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 4:37 [PATCH 1/2] tracing: show size of requested buffer Robin H. Johnson
2021-08-31 4:37 ` [PATCH 2/2] tracing: increase PERF_MAX_TRACE_SIZE to handle Sentinel1 and docker together Robin H. Johnson
2021-09-08 1:24 ` [PATCH 1/2] tracing: show size of requested buffer Steven Rostedt
2021-10-07 7:11 ` Peter Zijlstra
2021-10-07 13:23 ` Steven Rostedt
2021-10-07 17:26 ` Robin H. Johnson
2021-10-08 22:13 ` Steven Rostedt
2021-10-09 0:21 ` Robin H. Johnson
2021-10-26 20:43 ` Steven Rostedt
2021-10-26 21:23 ` Peter Zijlstra
2021-10-26 21:26 ` Steven Rostedt [this message]
2021-10-06 22:26 ` Steven Rostedt
2021-10-06 22:48 ` Robin H. Johnson
2021-10-07 0:55 ` Steven Rostedt
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=20211026172637.65f576c3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rjohnson@digitalocean.com \
--cc=robbat2@gentoo.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;
as well as URLs for NNTP newsgroup(s).