Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2989678ybi; Mon, 17 Jun 2019 14:10:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqxyG5WqKlto7774p5WdaQ0zpLcZN7IwcTaVSKX9kaP9URYrexi4xz5N3TX1kD02I4qXwWmH X-Received: by 2002:a17:902:e20f:: with SMTP id ce15mr3092551plb.112.1560805810392; Mon, 17 Jun 2019 14:10:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560805810; cv=none; d=google.com; s=arc-20160816; b=lVe4XtSWzeIFlzfIVq3Y4+dJU2KlBXQxGWpZlgohQnyJORGW5tldgmEQfRPwlwRTDg Hz70sXpfUQtF1IfT1e6PtVdCXZfqzQKfmFbL5B4rb6zR4AnvTgARIRVPuBKtcJ5PxyqW i9BjxHWEQkpuGkUXrzkQ3QoVr9DRvtNHTpoA4wIQfrWWeHkhzjz+sKI/mcuAaZ6sT8pN 5esA0L/SQM9TEYtrWSl62HXN+NOrUIG9MTuHQ7AkZuxA6QEH6v50ufblzoyq1Wucgv4l EDncvUl0vcNdBzHr6HHD4lqx2xAISXEARZI2pA7oYrDcG+h8qnEBAbviwJD0qtcYJafQ FUDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=CcTXKObVvvGufABik0hssBM7LaPYI847O97ZLUHV8dQ=; b=NSuvK/ISsia+7p+zoiBqMevJKt7ZY0Rmt4EQEJzIHAkao6CdG702SmxgKsG+h01nwg CupkyjFpFX4+RPKDx9SbutEuatO0g5vAqyQr6m1dXM8OMVZeTFLAzAdi/T9Ae9xAolb6 5C6e0vuv1dbiy8wGZTkvAuUuF0AhAKVW3QS2hQGozVgVmeme6CtkwTQCgF5fGzdob5zq OppEemBgQysSZ3wTuZlGNlHar8sE3PYuWkSC+XPoMAhjfs0NPh3KeUS20mdZU5kBAAs2 s4RPBB9nzUCyqEP4nMSx3YX9XWbSNR8yb8RRbnYgQkH2B1en1Y70L19SUpVT0mPAZEQP EmbQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l67si11741841plb.370.2019.06.17.14.09.54; Mon, 17 Jun 2019 14:10:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727875AbfFQVJi (ORCPT + 99 others); Mon, 17 Jun 2019 17:09:38 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:45712 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbfFQVJh (ORCPT ); Mon, 17 Jun 2019 17:09:37 -0400 Received: from p5b06daab.dip0.t-ipconnect.de ([91.6.218.171] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hcyse-0005Xx-QB; Mon, 17 Jun 2019 23:09:33 +0200 Date: Mon, 17 Jun 2019 23:09:32 +0200 (CEST) From: Thomas Gleixner To: John Ogness cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Petr Mladek , Sergey Senozhatsky , Steven Rostedt , Linus Torvalds , Greg Kroah-Hartman , Andrea Parri , Sergey Senozhatsky Subject: Re: [RFC PATCH v2 0/2] printk: new ringbuffer implementation In-Reply-To: <20190607162349.18199-1-john.ogness@linutronix.de> Message-ID: References: <20190607162349.18199-1-john.ogness@linutronix.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 7 Jun 2019, John Ogness wrote: Polite ping .... > This is a follow-up RFC on the work to reimplement much of > the core of printk. The original thread can be seen here[0]. > > One of the results of that thread was that the work needs to > be broken up into several pieces. A roadmap was laid out[1] > and this RFC is for the base component of the first piece: > a new ringbuffer implementation for printk. > > This series does not touch any existing printk code. It is > only the ringbuffer implementation. I am particularly > interested in feedback relating to the design of the > ringbuffer and the use of memory barriers. > > The series also includes a test module that performs some > heavy writer stress testing. I have successfully run these > tests on a 16-core ARM64 platform. > > John Ogness > > [0] https://lkml.kernel.org/r/20190212143003.48446-1-john.ogness@linutronix.de > [1] https://lkml.kernel.org/r/87y35hn6ih.fsf@linutronix.de > > John Ogness (2): > printk-rb: add a new printk ringbuffer implementation > printk-rb: add test module > > Documentation/core-api/index.rst | 1 + > Documentation/core-api/printk-ringbuffer.rst | 104 +++ > include/linux/printk_ringbuffer.h | 238 +++++++ > lib/Makefile | 2 + > lib/printk_ringbuffer.c | 924 +++++++++++++++++++++++++++ > lib/test_prb.c | 237 +++++++ > 6 files changed, 1506 insertions(+) > create mode 100644 Documentation/core-api/printk-ringbuffer.rst > create mode 100644 include/linux/printk_ringbuffer.h > create mode 100644 lib/printk_ringbuffer.c > create mode 100644 lib/test_prb.c > > -- > 2.11.0 > >