From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932555AbcASRmv (ORCPT ); Tue, 19 Jan 2016 12:42:51 -0500 Received: from mail-pf0-f181.google.com ([209.85.192.181]:33221 "EHLO mail-pf0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932271AbcASRmo (ORCPT ); Tue, 19 Jan 2016 12:42:44 -0500 Date: Tue, 19 Jan 2016 09:42:40 -0800 From: Alexei Starovoitov To: Wang Nan Cc: peterz@infradead.org, ast@kernel.org, linux-kernel@vger.kernel.org, He Kuang , Arnaldo Carvalho de Melo , Brendan Gregg , Jiri Olsa , Masami Hiramatsu , Namhyung Kim , Zefan Li , pi3orama@163.com Subject: Re: [PATCH 0/6] perf core: Read from overwrite ring buffer Message-ID: <20160119174239.GA83683@ast-mbp.thefacebook.com> References: <20160118120230.GP6357@twins.programming.kicks-ass.net> <1453202210-134429-1-git-send-email-wangnan0@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1453202210-134429-1-git-send-email-wangnan0@huawei.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 19, 2016 at 11:16:44AM +0000, Wang Nan wrote: > This patchset introduces two methods to support reading from overwrite. > > 1) Tailsize: write the size of an event at the end of it > 2) Backward writing: write the ring buffer from the end of it to the > beginning. what happend with your other idea of moving the whole header to the end? That felt better than either of these options.