From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Steven Rostedt" <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <peterz@infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Mathieu Desnoyers" <compudj@krystal.dyndns.org>,
"Pekka Paalanen" <pq@iki.fi>, "Martin Bligh" <mbligh@google.com>
Subject: Re: [PATCH 0/2] ring_buffer: updates for linux-tip
Date: Wed, 1 Oct 2008 09:20:52 +0200 [thread overview]
Message-ID: <c62985530810010020u1f3f44e1l6b8fb2f31c35d215@mail.gmail.com> (raw)
In-Reply-To: <20081001042951.412019606@goodmis.org>
2008/10/1 Steven Rostedt <rostedt@goodmis.org>:
> The first patch is just a lockdep clean up of the ring buffer.
>
> The next patch is a new locking design. It is not lockless (yet) but
> the locking is a bit cleaner than the original. The basic idea is
> that the reader now has its own page to read from that is not in
> the ring buffer. When the reader (a consumer) finishes a page, it
> then grabs a lock to pull out a new page from the ring buffer and
> replace it with the one that it just finished reading.
Good idea! Sounds a real saner approach.
next prev parent reply other threads:[~2008-10-01 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 4:29 [PATCH 0/2] ring_buffer: updates for linux-tip Steven Rostedt
2008-10-01 4:29 ` [PATCH 1/2] ring_buffer: remove raw from local_irq_save Steven Rostedt
2008-10-01 5:52 ` Ingo Molnar
2008-10-01 6:08 ` Ingo Molnar
2008-10-01 6:14 ` Ingo Molnar
2008-10-01 4:29 ` [PATCH 2/2] ring_buffer: implement new locking Steven Rostedt
2008-10-01 6:01 ` Ingo Molnar
2008-10-01 7:20 ` Frédéric Weisbecker [this message]
2008-10-01 7:23 ` [PATCH 0/2] ring_buffer: updates for linux-tip Ingo Molnar
2008-10-01 12:32 ` Frédéric Weisbecker
2008-10-01 17:08 ` Frédéric Weisbecker
2008-10-01 17:14 ` [PATCH] ftrace: preempt disable over interrupt disable 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=c62985530810010020u1f3f44e1l6b8fb2f31c35d215@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).