public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <srostedt@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/3] ring-buffer: make lockless
Date: Wed, 8 Jul 2009 17:05:22 -0400	[thread overview]
Message-ID: <20090708210522.GA17430@Krystal> (raw)
In-Reply-To: <20090708201445.696220393@goodmis.org>

* Steven Rostedt (rostedt@goodmis.org) wrote:
> From: Steven Rostedt <srostedt@redhat.com>
> 
> This patch converts the ring buffers into a completely lockless
> buffer recording system. The read side still takes locks since
> we still serialize readers. But the writers are the ones that
> must be lockless (those can happen in NMIs).

Hi Steven,

Have you started modeling this scheme with Promela as I previously
discussed with you ? Paul McKenney did a lot of nice papers on the
topic, and given the complexity level of this lockless buffering
algorithm, I'd be much more comfortable if it was formally verified. The
idea here is to make sure we don't start an endless bug-chasing hunt as
trace buffers gets more exposure to various workloads.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2009-07-08 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 20:13 [PATCH 0/3] [GIT PULL] rebase of lockless ring buffer Steven Rostedt
2009-07-08 20:13 ` [PATCH 1/3] ring-buffer: make the buffer a true circular link list Steven Rostedt
2009-07-08 20:13 ` [PATCH 2/3] ring-buffer: make lockless Steven Rostedt
2009-07-08 21:05   ` Mathieu Desnoyers [this message]
2009-07-08 21:16     ` Steven Rostedt
2009-07-08 20:13 ` [PATCH 3/3] ring-buffer: add design document Steven Rostedt
2009-07-10 11:31 ` [PATCH 0/3] [GIT PULL] rebase of lockless ring buffer Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2009-06-10 19:53 [PATCH 0/3] [GIT PULL][for 2.6.32] " Steven Rostedt
2009-06-10 19:53 ` [PATCH 2/3] ring-buffer: make lockless 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=20090708210522.GA17430@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    /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