Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752544AbYJDGCX (ORCPT ); Sat, 4 Oct 2008 02:02:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751177AbYJDGCN (ORCPT ); Sat, 4 Oct 2008 02:02:13 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:60838 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906AbYJDGCN (ORCPT ); Sat, 4 Oct 2008 02:02:13 -0400 Message-Id: <20081004060057.660306328@goodmis.org> User-Agent: quilt/0.46-1 Date: Sat, 04 Oct 2008 02:00:57 -0400 From: Steven Rostedt To: linux-kernel@vger.kernel.org Cc: Ingo Molnar , Thomas Gleixner , Peter Zijlstra , Andrew Morton , Linus Torvalds , Mathieu Desnoyers Subject: [PATCH 0/3] ring-buffer: less locking and only disable preemption Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 895 Lines: 24 Ingo, These patches need to be put through the ringer. Could you add them to your ring-buffer branch, so we can test them out before putting them into your master branch. The following patches bring the ring buffer closer to a lockless solution. They move the locking only to the actual moving the tail/write pointer from one page to the next. Interrupts are now enabled during most of the writes. A lot of the locking protection is still within the ftrace infrastructure. The last patch takes some of that away. The function tracer cannot be reentrant just due to the nature that it traces everything, and can cause recursion issues. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/