Sponsored Content
Full Discussion: Limit RAM Usages
Operating Systems Linux Red Hat Limit RAM Usages Post 302630609 by Shirishlnx on Thursday 26th of April 2012 04:49:26 AM
Old 04-26-2012
Thanks for clearing this . can you pls let me confirm ..

Code:
 
RAM: 1GB
Swap: 2GB
Kernel: 2.6.3
 
AND 
# cat /proc/sys/vm/min_free_kbytes
3794

So what basis this calculated and am missing logic behind same ..some docx state that it's number of pages of physical RAM available .

What logic used to calculate this value .. ??
 

10 More Discussions You Might Find Interesting

1. Programming

getting RAM size

Sir, How can i get the RAM size .Is there is any predefined function ..Howsir??? Thanks In advance, ArunKumar (6 Replies)
Discussion started by: arunkumar_mca
6 Replies

2. Solaris

Usages of Array's (Important please)

;) Hi friends, any one please help me. I want to store some job names into an array and also I want extract these names on different timings for scheduling. Please give me some idea. your's loving LOVE :p (1 Reply)
Discussion started by: Love
1 Replies

3. Linux

Built in ram limit for 64 bit

Hey all, I have been thinking about getting a new computer, and the motherboard I am looking at is capable of holding up to 8 Gb of ram. Now it appears as though for 32 bit linux, in order to use more than 4 Gb of ram, you had to enable a certain option in the kernel, but if I remember... (2 Replies)
Discussion started by: kermit
2 Replies

4. Red Hat

red hat Linux 5.0 is detecting 3gb ram but physical ram is 16gb

Hi, On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies

5. AIX

[AIX] usages of lint for .cpp file?

Hi , I Want to apply AIX lint to my source code which all are *.cpp/*.h >lint test.cpp lint: 1286-332 File test.cpp must have a .c, .C or .ln extension. It is ignored. lint: 1286-334 There are no files to process. I am getting above error. -Ashok (3 Replies)
Discussion started by: ashokd001
3 Replies

6. Solaris

How get memory and cpu usages of user's processes?

I have the processes (100+) by the oracle id and I'd to get the summarized view of the oracle processes' usage of the memory and the cpu. top would give me some, but not all. Thanks (3 Replies)
Discussion started by: iwmi
3 Replies

7. Solaris

Limit: stacksize: Can't remove limit

Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine? Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies

8. Red Hat

Physical RAM

Hi, I have a server (BL460c) with 32G of physical RAM. It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications. If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies

9. Shell Programming and Scripting

help me for Perl script for tool usages

Hi, How to do Perl script for floating license usages metric. Anyone help me out this issue? Regards, Ram. (0 Replies)
Discussion started by: ramanthan
0 Replies

10. Cybersecurity

Limit CPU and RAM utilization for new user in RedHat

We have a system with 4 Xeon Processors each with 10 cores, total 512 GB RAM and 10 TB Hard Drive. we want to create multiple user accounts with different resource limitations as : User 1: RAM : 50GB, PROCESSOR: 10 Cores , User folder in home directory of 10GB space. User 2: RAM :... (5 Replies)
Discussion started by: vaibhavvsk
5 Replies
KERNEL-COMMAND-LINE(7)						kernel-command-line					    KERNEL-COMMAND-LINE(7)

NAME
kernel-command-line - Kernel command line parameters SYNOPSIS
/proc/cmdline DESCRIPTION
The kernel, the initial RAM disk (initrd) and basic userspace functionality may be configured at boot via kernel command line arguments. For command line parameters understood by the kernel, please see kernel-parameters.txt[1] and bootparam(7). For command line parameters understood by the initial RAM disk, please see dracut.cmdline(7), or the documentation of the specific initrd implementation of your installation. CORE OS COMMAND LINE ARGUMENTS
systemd.unit=, rd.systemd.unit=, systemd.dump_core=, systemd.crash_shell=, systemd.crash_chvt=, systemd.confirm_spawn=, systemd.show_status=, systemd.log_target=, systemd.log_level=, systemd.log_color=, systemd.log_location=, systemd.default_standard_output=, systemd.default_standard_error=, systemd.setenv= Parameters understood by the system and service manager to control system behavior. For details, see systemd(1). quiet Parameter understood by both the kernel and the system and service manager to control console log verbosity. For details, see systemd(1). debug Parameter understood by both the kernel and the system and service manager to control console log verbosity. For details, see systemd(1). -b, emergency, single, s, S, 1, 2, 3, 4, 5 Parameters understood by the system and service manager, as compatibility options. For details, see systemd(1). locale.LANG=, locale.LANGUAGE=, locale.LC_CTYPE=, locale.LC_NUMERIC=, locale.LC_TIME=, locale.LC_COLLATE=, locale.LC_MONETARY=, locale.LC_MESSAGES=, locale.LC_PAPER=, locale.LC_NAME=, locale.LC_ADDRESS=, locale.LC_TELEPHONE=, locale.LC_MEASUREMENT=, locale.LC_IDENTIFICATION= Parameters understood by the system and service manager to control locale and language settings. For details, see systemd(1). fsck.mode= Parameter understood by the file system checker services. For details, see systemd-fsck@.service(8). quotacheck.mode= Parameter understood by the file quota checker service. For details, see systemd-quotacheck.service(8). systemd.journald.forward_to_syslog=, systemd.journald.forward_to_kmsg=, systemd.journald.forward_to_console= Parameters understood by the journal service. For details, see systemd-journald.service(8). vconsole.keymap=, vconsole.keymap.toggle=, vconsole.font=, vconsole.font.map=, vconsole.font.unimap= Parameters understood by the virtual console setup logic. For details, see systemd-vconsole-setup.service(8). udev.log-priority=, rd.udev.log-priority=, udev.children-max=, rd.udev.children-max=, udev.exec-delay=, rd.udev.exec-delay=, net.ifnames= Parameters understood by the device event managing daemon. For details, see systemd-udevd.service(8). plymouth.enable= May be used to disable the Plymouth boot splash. For details, see plymouth(8). luks=, rd.luks=, luks.crypttab=, rd.luks.crypttab=, luks.uuid=, rd.luks.uuid=, luks.options=, rd.luks.options=, luks.key=, rd.luks.key= Configures the LUKS full-disk encryption logic at boot. For details, see systemd-cryptsetup-generator(8). fstab=, rd.fstab= Configures the /etc/fstab logic at boot. For details, see systemd-fstab-generator(8). modules-load=, rd.modules-load= Load a specific kernel module early at boot. For details, see systemd-modules-load.service(8). SEE ALSO
systemd(1), bootparam(7), dracut.cmdline(7), systemd-fsck@.service(8), systemd-quotacheck.service(8), systemd-journald.service(8), systemd- vconsole-setup.service(8), systemd-udevd.service(8), plymouth(8), systemd-cryptsetup-generator(8), systemd-fstab-generator(8), systemd- modules-load.service(8) NOTES
1. kernel-parameters.txt https://www.kernel.org/doc/Documentation/kernel-parameters.txt systemd 208 KERNEL-COMMAND-LINE(7)
All times are GMT -4. The time now is 08:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy