Re: log-buf-len dynamic

[Andrea Arcangeli <andrea@suse.de>]

On Tue, Sep 23, 2003 at 05:01:26PM +0200, Jan Evert van Grootheest wrote:
> Andrea,
> 
> since you ask...
> I consider myself a not very typical Linux user in that I am a 
> programmer too and I (sometimes) write programs for Linux as well. And 
> yes, I do compile my own kernels.
> 
> I think it is pretty senseless to have a configuation option for the 
> default size of that buffer. Especially if I can, in one of the first rc 
> scripts, do something like 'echo 128 > /proc/sys/kernel/printkbuffer'.

having a sysctl can be an additional option (though it's tricky to
implement due the needed callbacks), but the problem I guess is that
most people needs a larger buf for the boot logs, so having only the
sysctl would be too late...

> The only hard requirement for that default size is that all output up 
> till that rc script fits into a buffer of that size.
> 
> And yes, I do care about that static 64K buffer. I still have an old 
> pentium that only has 16M. Every byte counts!

Note however that on the old 16M pentium it's unlikely that your boot
logs will overflow the current 64k, so for your pentium I doubt there
would be any need to use the feature. At least from my point of view the
feature is meant mainly for the high end, like 16/32-way HT with 64G of
ram etc.. where 64k hardly matters.

> On the other hand there are the really large systems with many CPUs and 
> such. Those might have problems with the small default. But, well, those 
> really could #ifdef a different default based on some configuration 
> options...

note the 64k are only wasted when you use the feature, there's nothing
wasted if you don't use it.

Andrea - If you prefer relying on open source software, check these links:
	    rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
	    http://www.cobite.com/cvsps/
	    svn://svn.kernel.org/linux-2.[46]/trunk