linux-kernel - Re: [PATCH 0/2] ring_buffer: updates for linux-tip

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081001072300.GD9366@elte.hu>
Date:	Wed, 1 Oct 2008 09:23:00 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frédéric Weisbecker <fweisbec@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	Pekka Paalanen <pq@....fi>, Martin Bligh <mbligh@...gle.com>
Subject: Re: [PATCH 0/2] ring_buffer: updates for linux-tip


* Frédéric Weisbecker <fweisbec@...il.com> wrote:

> 2008/10/1 Steven Rostedt <rostedt@...dmis.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.

are the tracer problems you've reported yesterday fixed in latest 
tip/master?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/