From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xen: increase static dmesg buffer to 64K
Date: Mon, 18 Jul 2011 10:16:28 +0200 [thread overview]
Message-ID: <20110718081628.GA22448@aepfle.de> (raw)
In-Reply-To: <4E23FD1B020000780004DD02@nat28.tlf.novell.com>
On Mon, Jul 18, Jan Beulich wrote:
> >>> On 17.07.11 at 17:43, Olaf Hering <olaf@aepfle.de> wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1310917380 -7200
> > # Node ID c6cade90d47f32e19f529930ba9f9acfa69f065f
> > # Parent 31dd84463eece20bd01c7aee22b52a0c06c67545
> > xen: increase static dmesg buffer to 64K
> >
> > On large systems the static dmesg buffer will overflow the 16K buffer, early
> > messages are lost. Increase the size to 64K to capture all lines on systems
> > without serial console.
>
> Please don't - on small systems it's a waste, and on even larger
> systems it still won't help. If anything, the dynamic allocation may
> need to happen earlier. As you probably saw, console_init_postirq()
> already sizes the buffer dependent on the number of CPUs in the
> system.
I think conring_size= should be evaluated very early. Is there a way to
allocate a range of mfns very early which can then be used for the dmesg
buffer?
Olaf
next prev parent reply other threads:[~2011-07-18 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 15:43 [PATCH] xen: increase static dmesg buffer to 64K Olaf Hering
2011-07-18 7:30 ` Jan Beulich
2011-07-18 8:16 ` Olaf Hering [this message]
2011-07-18 8:31 ` Jan Beulich
2011-07-18 8:33 ` Keir Fraser
2011-07-18 8:45 ` Olaf Hering
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=20110718081628.GA22448@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.