From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, Andrew Morton <akpm@digeo.com>
Subject: Re: [PATCH] move LOG_BUF_SIZE to header file
Date: 17 Dec 2002 01:39:33 -0500 [thread overview]
Message-ID: <m3isxtm9ne.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0212121517300.19827-100000@dragon.pdx.osdl.net>
I was just looking at doing that.
I'd suggest including CONFIG_CRYPTO_TEST in the default size
determination, and allowing both smaller sizes (for low ram
applications, such as embedded systems) and larger ones.
With all of the crypto =y, the test wipes everything before ACPI out
of the buffer before syslogd gets to start and log the buffer to disk.
Even with a 64k buffer.
-JimC
next prev parent reply other threads:[~2002-12-17 6:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 19:16 Randy.Dunlap
2002-12-10 19:41 ` Andrew Morton
2002-12-17 6:11 ` [PATCH] " Randy.Dunlap
2002-12-17 6:39 ` James H. Cloos Jr. [this message]
2002-12-17 17:22 ` Randy.Dunlap
2002-12-17 9:41 ` Christoph Hellwig
2002-12-17 17:14 ` Randy.Dunlap
2002-12-17 17:27 ` Andrew Morton
2002-12-17 22:33 ` [PATCH] (v3) move LOG_BUF_SIZE to header/config Randy.Dunlap
2002-12-18 1:14 ` Andrew Morton
2002-12-18 4:03 ` Randy.Dunlap
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=m3isxtm9ne.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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
Powered by JetHome