Re: cvs commit: src/sys/amd64/include param.h src/sys/arm/include param.h src/sys/i386/include param.h src/sys/ia64/include param.h src/sys/powerpc/include param.h src/sys/sparc64/include param.h src

John Birrell wrote: jb 2008-03-27 05:03:26 UTC FreeBSD src repository Modified files: sys/amd64/includeparam.h sys/arm/include param.h sys/i386/include param.h sys/ia64/include param.h sys/powerpc/include param.h sys/sparc64/include

Re: cvs commit: src/sys/amd64/include param.h src/sys/arm/include param.h src/sys/i386/include param.h src/sys/ia64/include param.h src/sys/powerpc/include param.h src/sys/sparc64/include param.h src/

On Thu, Mar 27, 2008 at 07:52:42AM +, Robert Watson wrote: Hmm. I think this probably is the right thing, but we'll need to be very careful to watch for people defining foo[MAXCPU] in globally visible data structures in the kernel in such a way that entries for the non-current CPU are

Re: cvs commit: src/sys/amd64/include param.h src/sys/arm/include param.h src/sys/i386/include param.h src/sys/ia64/include param.h src/sys/powerpc/include param.h src/sys/sparc64/include param.h src/

On Thu, Mar 27, 2008 at 08:42:11AM -0700, Sam Leffler wrote: What is the impact on UP+small systems? Those of us building for embedded applications are already fighting the existing bloat in the kernel. I don't think this is a big deal for UP+small systems because they probably don't allocate

cvs commit: src/sys/amd64/include param.h src/sys/arm/include param.h src/sys/i386/include param.h src/sys/ia64/include param.h src/sys/powerpc/include param.h src/sys/sparc64/include param.h src/sys/

jb 2008-03-27 05:03:26 UTC FreeBSD src repository Modified files: sys/amd64/includeparam.h sys/arm/include param.h sys/i386/include param.h sys/ia64/include param.h sys/powerpc/include param.h sys/sparc64/include param.h