I've created a vnode image (md0) with sectorsizes of 8192 and 4096
After installing MBR's bootcode '/boot/boot0', in provider 'md0' I did:
# boot0cfg -o noupdate -m 0xc md0
boot0cfg: read /dev/md0: Invalid argument
# boot0cfg -v md0
boot0cfg: read /dev/md0: Invalid argument
If custom sectorsize i
I have a few vms with "only" 768MB to 1GB of ram. The problem is
that buildworld is slow unless I give make(1) a jobs arg of about
8. However now when it reaches the c++ part of the build, it starts
to page like crazy:
Mem: 495M Active, 47M Inact, 162M Wired, 20M Cache, 85M Buf, 1624K Free
Swap:
On 3/25/2012 11:10 AM, Alfred Perlstein wrote:
It's kind of insane how much memory the compiler uses these days.
Any other options?
Switch to clang which uses less memory, or use a smaller jobs number.
Memory use is inevitable, but the benefit is more efficient binaries.
On Sun, Mar 25, 2012 at 9:37 AM, Joshua Isom wrote:
> On 3/25/2012 11:10 AM, Alfred Perlstein wrote:
>>
>> It's kind of insane how much memory the compiler uses these days.
>>
>> Any other options?
>
> Switch to clang which uses less memory, or use a smaller jobs number. Memory
> use is inevitable
After having a thought about this issue and also currently looking at a
BootEasy boot manager ...
'boot0cfg' is almost perfect for this task and should/could be "exploited".
It's '-o noupdate' already does a major task, of keeping main slice active.
Now all we need is a flag, through which we spe
I want to write a 64-bit version of the driver, the MAKEFILE on how to
write?I can compile 64-bit version of the driver in the 32 system?
Thank you!
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
--- On Sat, 3/24/12, Konstantin Belousov wrote:
> No, I mentioned exactly this in paragraph you replied to.
> To actually start executing from runq, thread needs to
> transition
> from kernel to userspace (in other words, thread appears on
> runq
> due to interrupt, thus entering kernel space)
7 matches
Mail list logo
