On Thu, 21 Dec 2023 12:58:13 -0500
Steven Rostedt wrote:
> On Thu, 21 Dec 2023 17:35:22 +
> Vincent Donnefort wrote:
>
> > @@ -5999,6 +6078,307 @@ int ring_buffer_subbuf_order_set(struct
> > trace_buffer *buffer, int order)
> > }
> > EXPORT_SYMBOL_GPL(ring_buffer_subbuf_order_set);
> >
On Thu, 21 Dec 2023 17:35:22 +
Vincent Donnefort wrote:
> @@ -5999,6 +6078,307 @@ int ring_buffer_subbuf_order_set(struct trace_buffer
> *buffer, int order)
> }
> EXPORT_SYMBOL_GPL(ring_buffer_subbuf_order_set);
>
The kernel developers have agreed to allow loop variables to be declared
On Thu, 21 Dec 2023 17:35:22 +
Vincent Donnefort wrote:
> @@ -739,6 +747,22 @@ static __always_inline bool full_hit(struct trace_buffer
> *buffer, int cpu, int f
> return (dirty * 100) > (full * nr_pages);
> }
>
> +static void rb_update_meta_page(struct ring_buffer_per_cpu *cpu_buff
In preparation for allowing the user-space to map a ring-buffer, add
a set of mapping functions:
ring_buffer_{map,unmap}()
ring_buffer_map_fault()
And controls on the ring-buffer:
ring_buffer_map_get_reader() /* swap reader and head */
Mapping the ring-buffer also involves:
A unique I
4 matches
Mail list logo
