Re: Random x86-64 seg-fault finally fixed

2010-12-26 Thread Tomas Bodzar
On Sun, Dec 26, 2010 at 8:44 AM, Chris Turner wrote: > Matthew Dillon wrote: >> >>    Partitioning is already >>    desireable for the current 48-core monster and I'd like to have >>    some sort of DragonFly host & guest solution that runs at full >>    performance on the bare HW without virtuali

Re: Random x86-64 seg-fault finally fixed

2010-12-26 Thread Matthew Dillon
:How would this be different than jail(8)? : :not understanding the 'without virtualization' part - :I know some form of HW virt a-la kvm has been discussed a few times - : :do you mean like segmenting the 'machine' or somesuch? Jail has no ability to segment kernel resources. It is really n

Re: Random x86-64 seg-fault finally fixed

2010-12-25 Thread Chris Turner
Matthew Dillon wrote: Partitioning is already desireable for the current 48-core monster and I'd like to have some sort of DragonFly host & guest solution that runs at full performance on the bare HW without virtualization. How would this be different than jail(8)? not understa

Re: Random x86-64 seg-fault finally fixed

2010-12-23 Thread Matthew Dillon
:Just out of curiosity, are there any plans for supporting :machines with 64 cores or even more? : :For example, the Sun Fire X4800 (quite common in larger data :centers) supports eight Xeon 7500 packages which have eight :cores plus hyperthreading, which gives a 128-way SMP system. :Solaris, Linu

Re: Random x86-64 seg-fault finally fixed

2010-12-23 Thread Oliver Fromme
Matthew Dillon wrote: > I also expect to have a fine-grained VM solution at least for standard > VM faults by the next release, hopefully sooner. It appears to be the > biggest bottleneck on the monster 48-core test box now. Just out of curiosity, are there any plans for supporting mach

Re: Random x86-64 seg-fault finally fixed

2010-12-22 Thread Tim Darby
Here's hoping everyone has an MPSAFE New Year! And I'm hoping one of these 48-core monsters shows up under my Christmas tree. Tim On Wed, Dec 22, 2010 at 1:19 PM, Matthew Dillon wrote: > The random utility seg-fault (usually cc1) on x86-64 appears to have > finally been fixed. It turned

Random x86-64 seg-fault finally fixed

2010-12-22 Thread Matthew Dillon
The random utility seg-fault (usually cc1) on x86-64 appears to have finally been fixed. It turned out to be a vm_page race in the pageout demon when it cycles pages onto the free page list. This clears the way for running the system with the remaining global tokens set to MPSAFE m