i already have ubuntu on my desktop.
i think i will try opensuse 64 bit |
Quote:
Quote:
|
Quote:
For a typical home user, video editing is at most a "maybe" for making good use of more than 3GB in one process. Everything else you do likely uses much less than 3GB per process even in a 64 bit Linux. There is no point worrying about the 3GB per process limit unless you actually want to run applications that make good use of more. Running multiple fairly big processes is more common than running any super big processes. So over 4GB physical ram is often useful even when over 3GB per process is not useful. |
I will try fedora 15 64 bit or opensuse 12.1 milstone 3
|
Quote:
Aside from video editing, and nasties like #dS max, you really need to be using multipule big processes to make use of anything like 6GB. Unless I'm mistaken the OP is using a laptop, and I wouldnt suggest running mutlipule huge processes on a laptop. Besides the heat issue, laptops are quite a bit slower than desktops. Might as well stop with 4GB unless you know you will be using huge processes, or running multipule big processes. |
Quote:
|
my swap is always 2GB,
if my RAM is big enough, i think the OS will not use swap at all. |
Hi, TigerLinux:
Quote:
Longer answer: The system *may* use swap for *other* things (for example, hibernation). But the short answer remains: if you have enough RAM, you won't use any swap. Quote:
Quote:
'Hope that helps .. PSM |
I think I will choose Fedora 15,
i hope it supports my nvidia GT525M graphics card and the intel core i5 integrated HD graphics too. |
"Back in the day," (yes, I remember it well... so there...) the IBM/360 (ahem...) had a 24-bit address bus. (Having "16 megabytes of memory" was inconceivable in the day when that "memory" was almost certainly magnetic core...) The entire CPU architecture was built around that (what would become a...) limitation.
Several generations of that processor architecture have followed, each one expanding upon its predecessors in a not-always-quite compatible way. The Intel processor family has patiently followed the same course: from the 8008 to the 8080 to the 8086 to the 80286/i286 to ... the 64-bit architectures of the present day. In every case, the single most important barricade that "got busted down" was memory capacity: how much RAM the processor could address, if it had it. Also in each case, the processor-architecture change was accompanied by a fundamentally new version of the operating system(s) in question: a version that was built for the new processor, and which required it. Linux is simply following that same familiar course. If you have a 64-bit capable CPU, you should be running a 64-bit capable Linux version on it. Only then can you access the full range of memory that the chip is capable of addressing. And, only then are you using that chip in its "native mode." |
Quote:
Quote:
Quote:
|
Quote:
I wanna only the nvidia GPU to work. |
Try http://www.omgubuntu.co.uk/2011/05/b...o-linux-users/ & post the results (please please please!). I have an optimus laptop on order and I am desperate to know if this works well enough to make my purchase worth while before it's too late to cancel!!
|
In my view,the differences between memory and swap space are obvious.
the cpu use the bus addressing the memory directly,and 32bit can address 4G theoretically ,but the detail amounts actually depends on the cpu and the os. to swap space ,we can simply treat it as a subsidiary memory,and regard it as a buffer of harddisk. when we don't have adequate memory,we can move parts of it bits into swap space fastly and move it back fastly when we need the bits.the swap space is just parts of disk,and cpu address it bits through memory,so it isn't included in the cpu addressing space. the swap space is just a os mechanism ,the memory addressing is a cpu mechanism in general. |
Quote:
|
All times are GMT -5. The time now is 08:08 PM. |