Bigmem support (4 gigas) is stable?
Hello I should add 1 giga of RAM to a machine which already has 1 giga. I know I will have to configure bigmem support in the kernel (2.2.19). I would like to know if this option is considered really stable and tested or I can expect some problems, because this is a heavy loaded critical server and in case of doubt I'll habilitate another server instead of giving more RAM to the one I already use. Thanks in advance - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Bigmem support (4 gigas) is stable?
Hello I should add 1 giga of RAM to a machine which already has 1 giga. I know I will have to configure bigmem support in the kernel (2.2.19). I would like to know if this option is considered really stable and tested or I can expect some problems, because this is a heavy loaded critical server and in case of doubt I'll habilitate another server instead of giving more RAM to the one I already use. Thanks in advance - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Calculation of private memory of processes for estimation of RAM in big server
I would like to know how to calculate the amount of private memory (i.e. memory used only by that process) so I can estimate the total amount of RAM I have to put in a heavy loaded server. In Sun Solaris I use a tool called pmap that gives me a resume of the private and shared memory and the size image of each process. This pmap utility uses the /proc filesystem to obtain the information. In Linux I've used ps axl and I think that the RSS column is the right one, but I'm not sure. Also I've look at the file /proc//status that has, for example, these lines: VmSize: 1144 kB VmLck: 0 kB VmRSS:52 kB VmData: 28 kB VmStk: 8 kB VmExe:56 kB VmLib: 1024 kB But again I'm not sure which one of these numbers is the one to look at. Could please any VM guru help with this? Please CC me because I'm not subscribed to the list Best regards Miquel Colom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Calculation of private memory of processes for estimation of RAM in big server
I would like to know how to calculate the amount of private memory (i.e. memory used only by that process) so I can estimate the total amount of RAM I have to put in a heavy loaded server. In Sun Solaris I use a tool called pmap that gives me a resume of the private and shared memory and the size image of each process. This pmap utility uses the /proc filesystem to obtain the information. In Linux I've used ps axl and I think that the RSS column is the right one, but I'm not sure. Also I've look at the file /proc/PID_OF_PROCESS/status that has, for example, these lines: VmSize: 1144 kB VmLck: 0 kB VmRSS:52 kB VmData: 28 kB VmStk: 8 kB VmExe:56 kB VmLib: 1024 kB But again I'm not sure which one of these numbers is the one to look at. Could please any VM guru help with this? Please CC me because I'm not subscribed to the list Best regards Miquel Colom - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5 VM
This is my first email to the list. I'm not subscribed but I've read it for years. I don't agree with those claiming that 2.4.xx is bad or still beta. We the administrators have the responsability to test early kernels and send good bug reports so the developers can solve the bugs. That's the way we can contribute to the community. But it's really risky to use these kernels on MAIN 24x7 production servers. This has been true for 1.2.x 2.0.x (I think that was the best linux kernel series) 2.2.x and 2.4.x and will be for 2.6.x also Given we know that the support from open source developers is clearly better than commercial contract supports, I don't see the reason to complain about the work of those wonderfull hackers spending their spare time coding for all of us. (I'm not subscribed to the list, Please CC me). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5 VM
This is my first email to the list. I'm not subscribed but I've read it for years. I don't agree with those claiming that 2.4.xx is bad or still beta. We the administrators have the responsability to test early kernels and send good bug reports so the developers can solve the bugs. That's the way we can contribute to the community. But it's really risky to use these kernels on MAIN 24x7 production servers. This has been true for 1.2.x 2.0.x (I think that was the best linux kernel series) 2.2.x and 2.4.x and will be for 2.6.x also Given we know that the support from open source developers is clearly better than commercial contract supports, I don't see the reason to complain about the work of those wonderfull hackers spending their spare time coding for all of us. (I'm not subscribed to the list, Please CC me). - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
