From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751431Ab0LUFNg (ORCPT ); Tue, 21 Dec 2010 00:13:36 -0500 Received: from mail-iw0-f174.google.com ([209.85.214.174]:40082 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750998Ab0LUFNe (ORCPT ); Tue, 21 Dec 2010 00:13:34 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=FhlFONY3bUo4VO6FpbpV/WlKhWuIQS29rShmBlLO7n94/s+smZBPDZGsuoSHbMHANQ cNJWL8tNAR8p62JVUWRlw8k8kw1gjyGbr2w/OAF5DSfXyPvyLbuS0y6Ea78F93ziMZBr PU4OenmWBLQKPbHVK94Id+wsFCftL6+bCFHWs= MIME-Version: 1.0 In-Reply-To: <1292892494.8743.76.camel@yhuang-dev> References: <4d0662e511688484b3@agluck-desktop.sc.intel.com> <4D0BEE1F.7020008@zytor.com> <20101219091752.GA16150@liondog.tnic> <1292813234.8743.66.camel@yhuang-dev> <1292892494.8743.76.camel@yhuang-dev> Date: Mon, 20 Dec 2010 21:13:33 -0800 X-Google-Sender-Auth: NAZI4ow2ZPWszT9PbDvBIUlmteo Message-ID: Subject: Re: [concept & "good taste" review] persistent store From: Tony Luck To: Huang Ying Cc: Borislav Petkov , Linus Torvalds , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , "linux-arch@vger.kernel.org" , "tglx@linutronix.de" , "mingo@elte.hu" , "greg@kroah.com" , "akpm@linux-foundation.org" , David Miller , Alan Cox , Jim Keniston , Kyungmin Park , Geert Uytterhoeven Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 20, 2010 at 4:48 PM, Huang Ying wrote: > If persistent storage driver (such as ERST) implements kmsg_dumper by > themselves, that should be easier to use multiple records for one > message dumping request. Or I can build it into the fs/pstore layer. If the record size looks too small[*], loop writing multiple records (starting with the tail of the buffer, so that if the persistent store fills up, we are sure to have the stack back trace and register dump). -Tony [*] "Too small" may be an architecture dependent value. Archs with a large number of registers (like ia64) might need more space than those with fewer registers.