• minor — The minor number of the device with this partition. This serves to separate the partitions
into different physical devices and relates to the number at the end of the name of the partition.
• #blocks — Lists the number of physical disk blocks contained in a particular partition.
• name — The name of the partition.
3.2.25. /proc/pci
This file contains a full listing of every PCI device on the system. Depending on the number of PCI
devices, /proc/pci can be rather long. A sampling of this file from a basic system looks similar to
the following:
Bus
0, device 0, function 0: Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev 3). Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe4000000 [0xe7ffffff].
Bus
0, device 1, function 0: PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge
(rev 3).
Master Capable. Latency=64. Min Gnt=128.
Bus
0, device 4, function 0: ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
Bus
0, device 4, function 1: IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1).
Master Capable. Latency=32. I/O at 0xd800 [0xd80f].
Bus
0, device 4, function 2: USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1). IRQ
5. Master Capable. Latency=32. I/O at 0xd400 [0xd41f].
Bus
0, device 4, function 3: Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2). IRQ 9.
Bus
0, device 9, function 0: Ethernet controller: Lite-On Communications Inc LNE100TX (rev
33). IRQ 5. Master Capable. Latency=32. I/O at 0xd000 [0xd0ff].
Bus
0, device 12, function
IRQ 11. Master Capable. Latency=32. Min Gnt=4.Max Lat=255.
This output shows a list of all PCI devices, sorted in the order of bus, device, and function. Beyond
providing the name and version of the device, this list also gives detailed IRQ information so an
administrator can quickly look for conflicts.
Tip
To get a more readable version of this information, type:
/sbin/lspci -vb
3.2.26. /proc/slabinfo
This file gives full information about memory usage on the slab level. Linux kernels greater than
version 2.2 use slab pools to manage memory above the page level. Commonly used objects have
their own slab pools.
Instead of parsing the highly verbose /proc/slabinfo file manually, the /usr/bin/slabtop
program displays kernel slab cache information in real time. This program allows for custom
configurations, including column sorting and screen refreshing.
A sample screen shot of /usr/bin/slabtop usually looks like the following example:
0: VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1).
/proc/pci
29
Need help?
Do you have a question about the ENTERPRISE LINUX 5 - DEPLOYMENT and is the answer not in the manual?
Questions and answers