Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758546Ab0LMRiM (ORCPT ); Mon, 13 Dec 2010 12:38:12 -0500 Received: from canuck.infradead.org ([134.117.69.58]:60068 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757393Ab0LMRiK convert rfc822-to-8bit (ORCPT ); Mon, 13 Dec 2010 12:38:10 -0500 Subject: Re: [PATCH 1/2] perf tools: Add reference timestamp to perf header From: Peter Zijlstra To: Frederic Weisbecker Cc: Arnaldo Carvalho de Melo , "David S. Ahern" , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20101213172349.GD1691@nowhere> References: <1291773285-16254-1-git-send-email-daahern@cisco.com> <1291773285-16254-2-git-send-email-daahern@cisco.com> <20101212201613.GA1784@nowhere> <4D06301C.2090309@cisco.com> <20101213155451.GA1691@nowhere> <20101213164854.GL5407@ghostprotocols.net> <20101213170923.GB1691@nowhere> <1292260289.6803.297.camel@twins> <1292260419.6803.300.camel@twins> <20101213172349.GD1691@nowhere> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Date: Mon, 13 Dec 2010 18:37:40 +0100 Message-ID: <1292261860.6803.338.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1509 Lines: 36 On Mon, 2010-12-13 at 18:23 +0100, Frederic Weisbecker wrote: > On Mon, Dec 13, 2010 at 06:13:39PM +0100, Peter Zijlstra wrote: > > On Mon, 2010-12-13 at 18:11 +0100, Peter Zijlstra wrote: > > > > > > Preferably, yes, but I don't see why we can't break the data file format > > > if we've got good reasons to. > > > > I mean, we pretty much _have_ to break data file format when we want to > > do splice() support. > > Because we'll have one file per-cpu? Right. > But perf.data on UP will be sensibly the same as today so I suspect > we won't need to be compatible. Nope, since one file simply doesn't scale, data-streams will have to live outside of the main file. And when you have to make that happen, there is no reason to maintain any kind of compatibility. The only thing you could do is provide some script to convert old data files to the new format. > But I guess I am missing something, in which case that probably doesn't > change much the picture. It's not because one day we'll need to break > the format that we can happily do so everyday. Backward compatibility > is important and we should preserve it when it's possible. But since you're all so focused on adding warts to the thing, maybe possible has sailed. But see my email to acme. -- 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/