Rollercoaster
-The BlacKCoaT Operative-
yes it will work fine.. dont depend on the seemingly hightech talk goin on
i assure u no one actually knows anything
i assure u no one actually knows anything
Exactly.. Even i thot that.. That's why i was confused when he mentioned them separately..mediator said:@kalpik : Users space is the user memory, where user apps can work and where swapping takes place.
Mediator the explanation given by you is theoretical but practically Linux kernel has a problem which was first identified in 2001. 32bit Linux Kernel splits the 4GB memory in two parts of 1GB and 3GB. Now kernel needs to map virtual space for every process to physically available memory but at any given point *unpatched* Linux kernel can map only 1GB of kernel virtual space to the physical memory. Further, out of this 1GB Memory, 128MB is reserved for storing memory mapping and paging table structures which is done only when kernel has to handle huge amounts of physical memory (>=1GB). This in turn means that Linux kernel can *effectively* access only 1GB - 128MB = 896MB of physical memory at any given time.mediator said:No eddie, >1GB ram doesn't necessarily means 64 bit system. There's no thumb rule in my knowledge, but all it has a little scientific explanation!
See 32 bit means 2^32 (2 raised to power 32) = 4,294,967,296 bytes and that's 4 GB.
SO u see a 32 bit system has a maximum supported RAM size of 4 GB.
Similarly 64 bit system has a max. supported RAM size of 2^64 = 18446744,073,709,551,616. I dunno how many billion terrabytes are these. I guess they call it 16 exabytes. Nice na?
Neways I dunno why u have written user space ad kernel space differently, both are just classifications of virtual memory .
Is it 64 bit HIGHMEM that u mistakenly typed as 64 GB?? IF not so, then how 4GB was increased to 64 GB? I didnt get this one!eddie said:support. 64GB HIGHMEM support was developed for processors like PentiumPro that were released with special instructions to address 4GB Memory limitation and increased it to 64GB.
It is not a bug but a limitation that has been addressed using patches. The current status is that both HIGHMEM 4GB and 64GB patches are present in official kernel. You can enable it if you have more than 1GB RAM but with earlier said kernel overload.mediator said:Hmmm......I didn't know something like that existed practically! Neways I'll be pleased if u enlighten me on following questions.
1. If the bug was founded in 2001, then whats the present status?
The answer lies in PentiumPro architecture and the PEA extension that it came with. These processors supported 36bit which translated into 64GB of physical memory support. Thus the kernel was made to support full memory range which could be supported by the processor but as the user land is 32bit, each process can't grow beyond 4GB. If you remember...this is why 36bit experiment of Intel failed miserably2. Is it 64 bit HIGHMEM that u mistakenly typed as 64 GB?? IF not so, then how 4GB was increased to 64 GB? I didnt get this one!
When we will near exabytes, I am sure we will know about the limitations and they will be dealt with accordinglyNeways I hope the thumb rule will be eliminated in future 32 bit Linuxes and I wonder if they are having trouble with 32 bit, then how'll they manage 64 bit and how'll they partition the exabytes!!
Well as per what's the discussion's going on you'd be better off using a 32-bit Linux. I can't explain you why, so well cos I personally don't have it clear in my mind.savithk said:i have a Q if i install 64bit linux . can i install 32bit linux software in 64bit linux. any linux64 is available on single CD.????
Hmm all right will search for it in free time. Maybe subscribe to gentoo-user mailing list too after the exams.eddie said:Actually I saw this discussion happening some months back on gentoo-user mailing list. At that time there were links to lkml archives and detailed explanations but I am somehow not able to find those mails. May be you can search lkml and gentoo-user archives?
If I get it right, highmem can break a few things. Is it?mediator said:@eddie, ok i got it! The 4GB memory can be accessed entirely in 32 bit now, and for greater than 4GB "32 bit+highmem patches" also work! Am i correct?
Yeah you got it more or lessmediator said:@eddie, ok i got it! The 4GB memory can be accessed entirely in 32 bit now, and for greater than 4GB "32 bit+highmem patches" also work! Am i correct?
It was developed as individual patch and then imported in official Kernel as an option.tech_your_future said:BTW, Highmem is a patch? Cos I have seen 'highmem' option while compiling the kernel, in it's description it says something like, to be used only if RAM is > 1GB.
This howto is not going to be a copy of the old one but will be updated. The old one was for Breezy and a lot has changed since Dapper was released. I have also tested this script with Edgy Knot 2 & 3 and have found no problems. The old one was "Firefox 1.5 with Flash and Java working 100% in amd64" howto by kurushi.
I do not recommend Swiftfox. The person who compiles it takes the FOSS Firefox code, then restricts other people from distributing it. This IMHO is perverting the license.
Well enough chatter, on to the howto *ubuntuforums.org/images/smilies/icon_biggrin.gif