search for: with_out_

Displaying 4 results from an estimated 4 matches for "with_out_".

Did you mean: _without_
2005 Jun 28
1
[OT] Memory Models and Multi/Virtual-Cores -- WAS: 4.0-> 4.1 update failing
...ith. > regards and TIA, At more than 1GiB on Linux/x86, you must use a 4G+4G kernel (this is the default) to see more than 960MiB. This causes a signficant (10%+) performance hit. On more than 4GiB, it is worsened as more extensive paging is used. If you have 1GiB or less, you should rebuild with_out_ "HIGHMEM" support which is a 1G+3G kernel, and you'll see better performance (and memory will be limited to 960MiB). In a nutshell, you should be running Linux/x86-64 on systems with more than 1GiB for optimal performance. If you have more than 4GiB of combined system and memory map...
2005 Jun 28
2
Offtopic Posts [was Re: [OT] Memory Models and Multi/Virtual-Cores -- WAS: 4.0 -> 4.1 update failing]
...ing a lot of the noise since people > continue to feed him. I assume the former is a reference to me. As far as the latter, you might re-think your singularity focus. As I've said before, you can't complain about me without complaining about others too. I.e., I try to point out things with_out_ going down into the tangent. Then people "get smart" with me believing what I say is not true. I can then either "let it go" and then people dismiss my offering of my experience and knowledge. Or I can correct them with the tangent. It's a catch-22 for all of us. > If p...
2005 Jun 02
16
Vote For CentOS :)
The "2005 Readers' Choice Awards" voting is in progress at Linux Journal, and CentOS is Nominated in the "distribution:" category. So ... all you guys and gals who think CentOS is the best thing ever, get over to: http://www.linuxjournal.com/article/8266 and vote for CentOS :) ------------------------------- Also, since write ins are allowed on the e-mailed ballot, if
2005 Jun 21
9
[OT] Memory Models and Multi/Virtual-Cores -- WAS: 4.0 -> 4.1 update failing
...ting instead of the common 40-50% for superscalar CISC or 60-70% for superscalar RISC. As an "added bonus," this means the 48-bit/256TiB constraint for PAE36 compatibility is _removed_. I.e., you can have a much larger, true memory pool, and any required windowing/ segmentation is done with_out_ paging by the "host" memory model, even though the OS is virtually running in a PAE36 or PAE52 model. This also gives rise to an entirely new platform for virtualization of simultaneous OSes -- be it the same OS, or different OSes. Because cores are virtual, you can have multiple, indepe...