Sponsored Content
Full Discussion: Help with ZFS arc cache
Operating Systems Solaris Help with ZFS arc cache Post 302479943 by radoulov on Monday 13th of December 2010 10:55:33 AM
Old 12-13-2010
There are additional notes on MOS about this.
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

UBC cache vs. Metadata cache

hi, What is the difference between UBC cache and Metadata cache ? where can i find UBC cache Hits and Metadata cache Hits in hp-ux? Advanced thanx for the help. (2 Replies)
Discussion started by: sushaga
2 Replies

2. Solaris

ARP Cache

Dear all, We are testing two of our servers for mq series connectivity. The scenario is, when one machine is shutting down it's services there are some scripts that do a dns update, which removes the ip address and relates it to the ip address of the other node on our dns server, and the update... (7 Replies)
Discussion started by: earlysame55
7 Replies

3. Linux

getting info on Cache Size, Data Cache etc..

Hi all I saw in Microsoft web site www.SysInternals.com a tool called CoreInfo from able to print out on screen the size of the Data and Instruction caches of your processor, the Locigal to Physical Processor mapping, the number of the CPU sockets. etc.. Do you know if in Linux is available a... (2 Replies)
Discussion started by: manustone
2 Replies

4. 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... (2 Replies)
Discussion started by: fugitive
2 Replies

5. Solaris

Zfs::zpool.cache file

Hi All, I am trying to read zpool.cache file to find out pool information like pool name, devices it uses and all properties. File seems to be in packed format.I am not sure how to unpack it. But from opensolaris code base we can see that they have used libz for uncompromising this file, but... (0 Replies)
Discussion started by: shailesh_111
0 Replies

6. Linux

File cache /Page cache Linux

Hi All, could any one point out any open source test-suites for "File cache" testing and as well as performance test suites for the same. Currently my system is up with Linux/ext4. Regards Manish (0 Replies)
Discussion started by: hmanish
0 Replies

7. Solaris

ZFS : Can arc size value exceed Physical RAM ?

Hi, kstat -p -m zfs -n arcstats -s size returns zfs:0:arcstats:size 8177310584 this values is approx (7.61 GB) but my Physical Memory size is only 6144 Megabytes. Can this happen ? if yes, then how can I find free memory on the system. BTW, I ran the kstat commands from a Non... (2 Replies)
Discussion started by: sapre_amit
2 Replies

8. UNIX for Beginners Questions & Answers

Check zfs cache usage for Solaris 11.3

Hi All, How do we calculate the zfs cache value from Solaris 11.3 ?? I normally use memstat but learnt that is not a good practice. Any other way to get the value ? (2 Replies)
Discussion started by: jayadanabalan
2 Replies
LOTRS(3)						 MBK LOGICAL STRUCTURE DEFINITIONS						  LOTRS(3)

NAME
lotrs - mbk logical transistor DESCRIPTION
The lotrs is used to describe a logical transistor. It is mostly used to describe leaf cells in terms of transistors interconnections, and as a result of layout extractions. Since the only target technology is CMOS, only NMOS and PMOS transistors are used. The declarations needed to work on lotrs are available in the header file "/labo/include/mlo.h". The following C structure supports the description of the logical transistor : typedef struct lotrs { struct lotrs *NEXT; struct locon *DRAIN; struct locon *GRID; struct locon *SOURCE; struct locon *BULK; char *TRNAME; long X,Y; unsigned short WIDTH, LENGTH; unsigned short PS, PD; unsigned short XS, XD; char TYPE; struct ptype *USER; } lotrs_list; NEXT Pointer to the next lotrs of the list. DRAIN Pointer to the drain connector of the transistor. This connector is, of course unique. See locon(3) for details. GRID Pointer to the grid connector of the transistor. This connector is, of course unique. See locon(3) for details. SOURCE Pointer to the source connector of the transistor. This connector is, of course unique. See locon(3) for details. BULK Pointer to the bulk connector of the transistor. This connector is, of course unique. See locon(3) for details. TRNAME Transistor instance name X, Y Coordinates of the transistor in a layout. These informations have sens only if the transistor netlist is the result of a layout extraction. They are otherwise set to zero. These coordinates are given in micron times the scale factor SCALE_X, since the extracted view is technology dependant. WIDTH, LENGTH Respectivly width and length of the transistor grid. PS, PD Respectivly perimeter of the source and drain, in micron times the scale factor SCALE_X. XS, XD These values are needed to compute respectivly the source and drain areas. Let As be the source area in square microns, and Width be the transistor grid width in micron, then lotrs->XS = As / Width * SCALE_X TYPE Canal type of the transistor. Six legal values are available : TRANSN N type MOS transistor TRANSP P type MOS transistor TRANSN_FAST High speed N type MOS transistor TRANSP_FAST High speed P type MOS transistor TRANSN_HVIO Low Leakage N type MOS transistor TRANSP_HVIO Low Leakage P type MOS transistor USER Pointer to a ptype list, see ptype(3) for details, that is a general purpose pointer used to share informations on the transistor. Remark : In integrated techniques, NMOS transistor bulk for digital circuits is always set to ground, and PMOS transistor bulk for digital circuits is always set to positive supply. SEE ALSO
mbk(1), addlotrs(3), dellotrs(3), locon(3), lofig(3), ptype(3). BUG REPORT
This tool is under development at the ASIM department of the LIP6 laboratory. We need your feedback to improve documentation and tools. ASIM
/LIP6 August 6, 2002 LOTRS(3)
All times are GMT -4. The time now is 10:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy