ZFS : Can arc size value exceed Physical RAM ? Post: 302713553

9 More Discussions You Might Find Interesting

1. Programming

Max file size can't exceed 2 GB

We have Sun OS 5.9 we are doing a backup process (ProC program) that uses the function... fprintf(fp,"%s;%s;%s;%s;%s;%ld;%ld;%ld;%ld;%s;%s;%s;%d;%s;%s;%s;%ld;%s;%s;%s;%ld;%ld;%s;%ld;%s;%ld;%s;%s;%c%c",x_contrno, x_subno, x_b_subno,x_transdate,x_last_traffic_date,BillAmt_s, x_billamount_int,...

2. Solaris

getting available physical RAM

What command should I be using on Solaris 9 to get an accurate representation of the available physical RAM?

3. Solaris

RAM Physical Memory usage by each Process.

Hi All, I am trying to find the physical memory usage by each process/users. Can you please let me know how to get the memory usage?. Thanks, bsraj.

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?

5. Solaris

ZFS ARC cache issue

We are having a server running zfs root with 64G RAM and the system has 3 zones running oracle fusion app and zfs cache is using 40G memory as per kstat zfs:0:arcstats:size. and system shows only 5G of memory is free rest is taken by kernel and 2 remaining zones. Now my problem is that...

6. Solaris

Solaris sun4v - how do you determine physical RAM?

I have a Sun T5120, and I want to programmatically determine how much RAM it has. # uname -a SunOS myhost 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5120 The box has 64Gb; I tried prtdiag and prtconf, but they give me bogus info prtconf gives me: # prtconf |grep -i...

7. Solaris

Help with ZFS arc cache

Greetings Forumers! I have a Solaris 10u9 M5000 with 32GB RAM and have noticed the ZFS arc cache is consuming large amount of memory. Here's what I see on my system: # echo ::memstat|mdb -k Page Summary Pages MB %Tot ------------ ---------------- ...

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...

9. UNIX for Advanced & Expert Users

Physical disk IO size smaller than fragment block filesystem size ?

Hello, in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ...

LEARN ABOUT CENTOS

mtrr_add

MTRR_ADD(9)							Hardware Interfaces						       MTRR_ADD(9)

NAME

       mtrr_add - Add a memory type region

SYNOPSIS

       int mtrr_add(unsigned long base, unsigned long size, unsigned int type, bool increment);

ARGUMENTS

       base
	   Physical base address of region

       size
	   Physical size of region

       type
	   Type of MTRR desired

       increment
	   If this is true do usage counting on the region

DESCRIPTION

       Memory type region registers control the caching on newer Intel and non Intel processors. This function allows drivers to request an MTRR
       is added. The details and hardware specifics of each processor's implementation are hidden from the caller, but nevertheless the caller
       should expect to need to provide a power of two size on an equivalent power of two boundary.

       If the region cannot be added either because all regions are in use or the CPU cannot support it a negative value is returned. On success
       the register number for this entry is returned, but should be treated as a cookie only.

       On a multiprocessor machine the changes are made to all processors. This is required on x86 by the Intel processors.

       The available types are

       MTRR_TYPE_UNCACHABLE - No caching

       MTRR_TYPE_WRBACK - Write data back in bursts whenever

       MTRR_TYPE_WRCOMB - Write data back soon but allow bursts

       MTRR_TYPE_WRTHROUGH - Cache reads but not writes

BUGS

       Needs a quiet flag for the cases where drivers do not mind failures and do not wish system log messages to be sent.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							       MTRR_ADD(9)