Sponsored Content
Operating Systems Linux Memory issue on My CentOS 5.8 x64 bit server Post 302770810 by radoulov on Monday 18th of February 2013 12:13:42 PM
Old 02-18-2013
Because the Linux kernel works that way, the cached memory is used to optimize access to slow access data, usually disks.
Most of that could be considered available ("free") memory.

Last edited by radoulov; 02-18-2013 at 01:21 PM..
 

8 More Discussions You Might Find Interesting

1. Linux

Memory issues iin CentOS release 5.3 (Final)

New to the forum. I am running CentOS release 5.3 (Final) and have run into a unique situation. I have been able to determine that we have a swap memory leak due to an issue with an asterisk server. This specific issue takes approximately 2-3 months for enough of the swap to to be used before... (1 Reply)
Discussion started by: g0neinsane
1 Replies

2. Red Hat

centOS memory leak - MEGABYTES per day

hi i've notice a huge problem on my newly installed centOS server and i have no idea how to solve it and where to start.. memory on server 3 GB and it goes down, down, down.. after reboot it shows 71mb used after a hour its 76mb and after 24h it's around 200 later = more i have NO idea... (7 Replies)
Discussion started by: tip78
7 Replies

3. Red Hat

Domain name server installation issue in centOS

HI All, I am trying to setup DNS on my centOS server. I am using bind software to setup DNS. The following errors have getting. ================================================== Error in named configuration: zone localdomain/IN: loaded serial 42 zone localhost/IN: loaded serial 42... (4 Replies)
Discussion started by: phpconnect
4 Replies

4. Red Hat

Centos 4 32 bit - New kernel ethX MAC address order issue

I have compiled a new kernel (3.2.9) for centos 4/5/6 servers. There is an issue with the centos 4, 32 bit servers. The kernel changes the order in which the MAC address is determined and because of this the server network does not come up as the wrong MAC address are assigned. Even if we specify... (6 Replies)
Discussion started by: anil510
6 Replies

5. UNIX for Advanced & Expert Users

Freeipa issue on Centos 6.3

Hi, We are configuring Freeipa for our LDAP system. Things seem to work okay when we try and log in with our domain accounts on the LDAP server. But when we try to loggon to the slave it closes the connection. There is an option in authconfig-tui to configure IPA. However, the senior admin... (0 Replies)
Discussion started by: mojoman
0 Replies

6. Filesystems, Disks and Memory

Maximum Memory RAM for windows 7 32 bit

Hi, i have just installed 4 gb RAM ddr3 on OS Windows 7 32 bit. In "manage peripherals" i see this section: Memory installed (ram) : 4,00 gb (2,30gb usable) Why only 2,30 gb usable ? In Windows 7 32bit the maximum size is not 3,00gb ? see file attached, please (4 Replies)
Discussion started by: nash83
4 Replies

7. UNIX for Advanced & Expert Users

Which memory test tool is popular on CentOS 6?

Hi, Which tools or method is popular, simple and effective, to check memory such as bad sector, throughput and performance? Thank you. - j (5 Replies)
Discussion started by: hce
5 Replies

8. AIX

Gdb on a 64 bit executable - cannot access memory

Hi, Can anyone explain this please..... A simple test program... ### snip #include <stdio.h> main() { static int n; n = 6; printf("hello %d\n", n); n=7; } ### snip 64 bit compile/link.... (2 Replies)
Discussion started by: bagpussnz
2 Replies
POSIX_FADVISE(2)					     Linux Programmer's Manual						  POSIX_FADVISE(2)

NAME
posix_fadvise - predeclare an access pattern for file data SYNOPSIS
#include <fcntl.h> int posix_fadvise(int fd, off_t offset, off_t len, int advice); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): posix_fadvise(): _XOPEN_SOURCE >= 600 || _POSIX_C_SOURCE >= 200112L DESCRIPTION
Programs can use posix_fadvise() to announce an intention to access file data in a specific pattern in the future, thus allowing the kernel to perform appropriate optimizations. The advice applies to a (not necessarily existent) region starting at offset and extending for len bytes (or until the end of the file if len is 0) within the file referred to by fd. The advice is not binding; it merely constitutes an expectation on behalf of the application. Permissible values for advice include: POSIX_FADV_NORMAL Indicates that the application has no advice to give about its access pattern for the specified data. If no advice is given for an open file, this is the default assumption. POSIX_FADV_SEQUENTIAL The application expects to access the specified data sequentially (with lower offsets read before higher ones). POSIX_FADV_RANDOM The specified data will be accessed in random order. POSIX_FADV_NOREUSE The specified data will be accessed only once. POSIX_FADV_WILLNEED The specified data will be accessed in the near future. POSIX_FADV_DONTNEED The specified data will not be accessed in the near future. RETURN VALUE
On success, zero is returned. On error, an error number is returned. ERRORS
EBADF The fd argument was not a valid file descriptor. EINVAL An invalid value was specified for advice. ESPIPE The specified file descriptor refers to a pipe or FIFO. (Linux actually returns EINVAL in this case.) VERSIONS
posix_fadvise() appeared in kernel 2.5.60. Glibc support has been provided since version 2.2. CONFORMING TO
POSIX.1-2001. Note that the type of the len argument was changed from size_t to off_t in POSIX.1-2003 TC1. NOTES
Under Linux, POSIX_FADV_NORMAL sets the readahead window to the default size for the backing device; POSIX_FADV_SEQUENTIAL doubles this size, and POSIX_FADV_RANDOM disables file readahead entirely. These changes affect the entire file, not just the specified region (but other open file handles to the same file are unaffected). POSIX_FADV_WILLNEED initiates a nonblocking read of the specified region into the page cache. The amount of data read may be decreased by the kernel depending on virtual memory load. (A few megabytes will usually be fully satisfied, and more is rarely useful.) In kernels before 2.6.18, POSIX_FADV_NOREUSE had the same semantics as POSIX_FADV_WILLNEED. This was probably a bug; since kernel 2.6.18, this flag is a no-op. POSIX_FADV_DONTNEED attempts to free cached pages associated with the specified region. This is useful, for example, while streaming large files. A program may periodically request the kernel to free cached data that has already been used, so that more useful cached pages are not discarded instead. Pages that have not yet been written out will be unaffected, so if the application wishes to guarantee that pages will be released, it should call fsync(2) or fdatasync(2) first. BUGS
In kernels before 2.6.6, if len was specified as 0, then this was interpreted literally as "zero bytes", rather than as meaning "all bytes through to the end of the file". SEE ALSO
readahead(2), sync_file_range(2), posix_fallocate(3), posix_madvise(3), feature_test_macros(7) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2010-09-20 POSIX_FADVISE(2)
All times are GMT -4. The time now is 02:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy