HP Visualize J5000 HP Workstations - Graphics Administration Guide For Red Hat - Page 24

Changing graphics shared memory size, Count transparent in overlay visual

Page 24 highlights

Changing graphics shared memory size The size of the shared memory segment used by the GRM can be controlled through a Server Option. The default value is 0x580000 (5.5 Mbytes) on Series 700 computers. Note: The actual GRM shared memory size on a system can be determined by running "ipcs -ma", finding the entry with CPID matching the process ID of the grmd process and then checking the segment size (SEGSZ) field. If more shared memory space is needed, graphics shared memory size can be increased. For example, to set it to eight megabytes: ServerOptions GraphicsSharedMemorySize=0x800000 The value must be in hexadecimal. The new value won't take effect until you restart the X Server. It is also possible to decrease the size of GRM shared memory. You may want to do this if you want to reduce the swap-space requirements of your system and/or you do not intend to run any 3D graphics processes. For example, you could reduce graphics shared memory size to 0x100000 (one megabyte). Count transparent in overlay visual In some configurations, an 8-plane overlay visual may have less than 256 colors. This should not cause a problem for most applications. If an application depends on 8-plane visuals having 256 colormap entries, this option may be useful. Setting this option will cause the X server to count transparent entries in the number of colormap entries. Examples of Relevant Graphics Devices: HP VISUALIZE-FX5 and FX10 X*screens File Screen Option To Use: CountTransparentInOverlayVisual Screen /dev/mem [DefaultVisual] Graphics Administration Guide For Red Hat Linux 6.2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73

Changing graphics shared memory size
The size of the shared memory segment used by the GRM can be controlled
through a Server Option. The default value is 0x580000 (5.5 Mbytes) on Series
700 computers.
_______________________________________________________________________
Note:
The actual GRM shared memory size on a system can be determined by
running "
ipcs -ma
", finding the entry with CPID matching the process ID of
the grmd process and then checking the segment size (
SEGSZ
) field.
________________________________________________________________________
If more shared memory space is needed, graphics shared memory size can be
increased. For example, to set it to eight megabytes:
ServerOptions
GraphicsSharedMemorySize=0x800000
The value must be in hexadecimal. The new value won't take effect until you
restart the X Server.
It is also possible to decrease the size of GRM shared memory.
You may want to
do this if you want to reduce the swap-space requirements of your system and/or
you do not intend to run any 3D graphics processes. For example, you could
reduce graphics shared memory size to 0x100000 (one megabyte).
Count transparent in overlay visual
In some configurations, an 8-plane overlay visual may have less than 256 colors.
This should not cause a problem for most applications. If an application depends
on 8-plane visuals having 256 colormap entries, this option may be useful. Setting
this option will cause the X server to count transparent entries in the number of
colormap entries.
Examples of Relevant Graphics Devices:
HP V
ISUALIZE
-FX
5
and FX
10
X*screens
File Screen Option To Use:
CountTransparentInOverlayVisual
Screen /dev/mem
[
DefaultVisual
]
Graphics Administration Guide For Red Hat Linux 6.2