07-15-2009
FreeBSD 7.2 build kernel benchmarks
Just for fun:
CPU/Speed: 2x AMD Opteron Model 2384 (2.7GHz/512KB) quad core processor
Ram: 4 x2GB ECC DDR2-667 single rank memory
in RAID 0 mode (strip 128KB, Read Caching enabled, Write Caching disabled) with 2 HDD, CPUTYPE=opteron, CFLAGS= -O2 -fno-strict-aliasing -pipe, CXXFLAGS+= -fconserve-space
Quote:
linking kernel.debug
text data bss dec hex filename
7269549 734623 371004 8375176 7fcb88 kernel.debug
objcopy --only-keep-debug kernel.debug kernel.symbols
objcopy --strip-debug --add-gnu-debuglink=kernel.symbols kernel.debug kernel
--------------------------------------------------------------
>>> Kernel build for SUNPAE completed on Tue Jun 30 10:44:44 CDT 2009
--------------------------------------------------------------
205.268u 25.273s 1:01.01 377.8% 6307+1041k 2910+1805io 193pf+0w
9 More Discussions You Might Find Interesting
1. BSD
Does anyone know how to enter the Kernel Configuration program in FreeBSD before installation to resolve conflicts of hardware?:confused: (3 Replies)
Discussion started by: Enoch Chan
3 Replies
2. BSD
# cd /usr/src/sys/i386/conf
# cp GENERIC LOVEPP
# cd /usr/src
# make buildkernel KERNCONF=LOVEPP
make:don't know how to make buildkernel. Stop
Any suggestions?
(I am using Freebsd4.8) (2 Replies)
Discussion started by: sheep
2 Replies
3. SCO
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies
4. UNIX for Advanced & Expert Users
I got the freebsd kernel source from the first install CD(in directory:\7.0-RELEASE\src\),isn't right? if so,how can i read it? Is there any tools? (1 Reply)
Discussion started by: zhouq3132
1 Replies
5. UNIX for Dummies Questions & Answers
I got the freebsd kernel source from the first install CD(in directory:\7.0-RELEASE\src\),isn't right? if so,how can i read it? Is there any tools? (4 Replies)
Discussion started by: zhouq3132
4 Replies
6. BSD
All,
I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server.
I managed to fix it by doing the following:
Booting into loader mode:
unload
set... (3 Replies)
Discussion started by: drbabbers
3 Replies
7. UNIX Benchmarks
Just for fun, I thought I'd post my output from `time make -j4 buildworld' and `time make -j4 buildkernel' and see if anyone else had any good times.
The machine is an Intel Core2Duo 2.2GHz with 2048MB DDR3.
--------------------------------------------------------------
>>> Kernel build... (1 Reply)
Discussion started by: glen.barber
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies
9. Linux
Hi,
Can i just ask how I can create a bootable PXE image from the built kernel source.
What files do I need to get?
Thanks! (1 Reply)
Discussion started by: h0ujun
1 Replies
LEARN ABOUT DEBIAN
go-testflag
GO-TESTFLAG(7) Miscellaneous Information Manual GO-TESTFLAG(7)
NAME
go - tool for managing Go source code
DESCRIPTION
The 'go test' command takes both flags that apply to 'go test' itself and flags that apply to the resulting test binary.
The test binary, called pkg.test, where pkg is the name of the directory containing the package sources, has its own flags:
-test.v
Verbose output: log all tests as they are run.
-test.run pattern
Run only those tests and examples matching the regular expression.
-test.bench pattern
Run benchmarks matching the regular expression. By default, no benchmarks run.
-test.cpuprofile cpu.out
Write a CPU profile to the specified file before exiting.
-test.memprofile mem.out
Write a memory profile to the specified file when all tests are complete.
-test.memprofilerate n
Enable more precise (and expensive) memory profiles by setting runtime.MemProfileRate. See 'godoc runtime MemProfileRate'. To pro-
file all memory allocations, use -test.memprofilerate=1 and set the environment variable GOGC=off to disable the garbage collector,
provided the test can run in the available memory without garbage collection.
-test.parallel n
Allow parallel execution of test functions that call t.Parallel. The value of this flag is the maximum number of tests to run
simultaneously; by default, it is set to the value of GOMAXPROCS.
-test.short
Tell long-running tests to shorten their run time. It is off by default but set during all.bash so that installing the Go tree can
run a sanity check but not spend time running exhaustive tests.
-test.timeout t
If a test runs longer than t, panic.
-test.benchtime n
Run enough iterations of each benchmark to take n seconds. The default is 1 second.
-test.cpu 1,2,4
Specify a list of GOMAXPROCS values for which the tests or benchmarks should be executed. The default is the current value of
GOMAXPROCS.
For convenience, each of these -test.X flags of the test binary is also available as the flag -X in 'go test' itself. Flags not listed
here are passed through unaltered. For instance, the command
go test -x -v -cpuprofile=prof.out -dir=testdata -update
will compile the test binary and then run it as
pkg.test -test.v -test.cpuprofile=prof.out -dir=testdata -update
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-TESTFLAG(7)