lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20231227095914.4ee69b53b69254ad8c5f7171@kernel.org> Date: Wed, 27 Dec 2023 09:59:14 +0900 From: Masami Hiramatsu (Google) <mhiramat@...nel.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org, Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>, Jonathan Corbet <corbet@....net>, Masami Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com> Subject: Re: [PATCH] ring-buffer/Documentation: Add documentation on buffer_percent file On Tue, 26 Dec 2023 12:35:25 -0500 Steven Rostedt <rostedt@...dmis.org> wrote: > From: "Steven Rostedt (Google)" <rostedt@...dmis.org> > > When the buffer_percent file was added to the kernel, the documentation > should have been updated to document what that file does. > Looks good to me. Acked-by: Masami Hiramatsu (Google) <mhiramat@...nel.org> Thanks! > Fixes: 03329f9939781 ("tracing: Add tracefs file buffer_percentage") > Signed-off-by: Steven Rostedt (Google) <rostedt@...dmis.org> > --- > Documentation/trace/ftrace.rst | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst > index 933e7efb9f1b..16eabb00fa55 100644 > --- a/Documentation/trace/ftrace.rst > +++ b/Documentation/trace/ftrace.rst > @@ -180,6 +180,21 @@ of ftrace. Here is a list of some of the key files: > Only active when the file contains a number greater than 0. > (in microseconds) > > + buffer_percent: > + > + This is the water-mark for how much the ring buffer needs to be filled > + before a waiter is woken up. That is, if an application call a > + blocking read syscall on one of the per_cpu trace_pipe_raw files, it > + will block until the given amount of data specified by buffer_percent > + is in the ring buffer before it wakes the reader up. This also > + controls how splice system calls are blocked on this file. > + > + 0 - means to wake up as soon as there is any data in the ring buffer. > + 50 - means to wake up when roughly half of the ring buffer sub-buffers > + are full. > + 100 - means to block until the ring buffer is totally full and is > + about to start overwriting the older data. > + > buffer_size_kb: > > This sets or displays the number of kilobytes each CPU > -- > 2.42.0 > > -- Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists