From: Huang Ying <ying.huang@intel.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>,
"greg@kroah.com" <greg@kroah.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
David Miller <davem@davemloft.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jim Keniston <jkenisto@linux.vnet.ibm.com>,
Kyungmin Park <kmpark@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store
Date: Tue, 21 Dec 2010 08:48:14 +0800 [thread overview]
Message-ID: <1292892494.8743.76.camel@yhuang-dev> (raw)
In-Reply-To: <AANLkTikULE_Jncjs=PkARjZyxb=f+t=4J8g8LQL+L=BZ@mail.gmail.com>
On Tue, 2010-12-21 at 01:19 +0800, Tony Luck wrote:
> On Sun, Dec 19, 2010 at 6:47 PM, Huang Ying <ying.huang@intel.com> wrote:
> > 8KB is about 100-200 lines message, sometimes it may be not enough for
> > all necessary information. But in fact, we can use multiple ERST
> > records to save one kernel message dumping. So the real limitation is
> > just total storage capacity.
>
> We can - but it will be a bit messy within my pstore + platform driver
> framework (I'd have to have erst tell pstore that it could handle some
> larger size, 2x or 3x the actual record size and then break a write
> into pieces. Presumably re-assemble on the read side too).
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.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2010-12-21 0:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 18:16 [concept & "good taste" review] persistent store Luck, Tony
2010-12-17 1:57 ` Linus Torvalds
2010-12-17 6:28 ` Tony Luck
2010-12-17 18:09 ` Tony Luck
2010-12-17 18:19 ` James Bottomley
2010-12-17 21:38 ` Linus Torvalds
2010-12-17 23:08 ` Tony Luck
2010-12-17 23:11 ` H. Peter Anvin
2010-12-17 23:53 ` Tony Luck
2010-12-18 18:23 ` Linus Torvalds
2010-12-18 23:06 ` Tony Luck
2010-12-19 9:17 ` Borislav Petkov
2010-12-19 17:01 ` Florian Mickler
2010-12-19 20:17 ` Tony Luck
2010-12-20 2:47 ` Huang Ying
2010-12-20 10:46 ` David Howells
2010-12-21 0:41 ` Huang Ying
2010-12-21 10:10 ` David Howells
2010-12-22 0:26 ` Huang Ying
2010-12-22 0:32 ` David Howells
2010-12-22 0:43 ` Huang Ying
2010-12-22 0:53 ` david
2010-12-22 7:34 ` Tony Luck
2010-12-20 17:19 ` Tony Luck
2010-12-21 0:48 ` Huang Ying [this message]
2010-12-21 5:13 ` Tony Luck
2010-12-21 7:42 ` Borislav Petkov
2010-12-20 7:26 ` Borislav Petkov
2010-12-20 17:18 ` Linus Torvalds
2010-12-20 18:58 ` Borislav Petkov
2010-12-20 21:09 ` Tony Luck
2010-12-20 10:49 ` David Howells
2010-12-20 16:52 ` Tony Luck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1292892494.8743.76.camel@yhuang-dev \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=jkenisto@linux.vnet.ibm.com \
--cc=kmpark@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony.luck@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox