HP Visualize J5000 hp workstations - hp-ux 10.20 graphics administration guide - Page 40

Shared Memory Usage With 3D Graphics, Changing Graphics Shared Memory Size

Get HP Visualize J5000 - Workstation PDF manuals and user guides View all HP Visualize J5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 40 highlights

For example: Screen /dev/crt/ ScreenOptions EnableIncludeInferiorsFix This gives a system administrator control over when the fix is active and when it is not. In this way, each site can evaluate whether or not it is beneficial to enable this fix. Shared Memory Usage With 3D Graphics Graphics processes use shared memory to access data pertaining to the display device and X11 resources created by the server. ("Resources" includes windows, colormaps, and cursors.) The X11 server initiates an independent process called the Graphics Resource Manager (GRM) to manage these resources among graphics processes. Graphics processes include PEXlib, PHIGS, and Starbase applications. One problem encountered with GRM shared memory is that it may not be large enough to run some applications. Graphics applications that require VM double-buffering use large amounts of shared memory. Shared memory can be completely consumed by several double-buffered graphics windows. When an application attempts to use more shared memory than is available, the application encounters errors and might terminate. You can circumvent the problem by using Server Options to change the shared memory size. 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 Note: The value must be in hexadecimal. The new value won't take effect until you restart the X Server Page 40 Graphics Administration Guide for HP-UX 10.20

  • 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
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
For example:
Screen /dev/crt/
ScreenOptions
EnableIncludeInferiorsFix
This gives a system administrator control over when the fix is active and when it is not. In this way, each
site can evaluate whether or not it is beneficial to enable this fix.
Shared Memory Usage With 3D Graphics
Graphics processes use shared memory to access data pertaining to the display device and X11 resources
created by the server. ("Resources" includes windows, colormaps, and cursors.) The X11 server initiates
an independent process called the Graphics Resource Manager (GRM) to manage these resources among
graphics processes. Graphics processes include PEXlib, PHIGS, and Starbase applications. One problem
encountered with GRM shared memory is that it may not be large enough to run some applications.
Graphics applications that require VM double-buffering use large amounts of shared memory. Shared
memory can be completely consumed by several double-buffered graphics windows. When an
application attempts to use more shared memory than is available, the application encounters errors and
might terminate.
You can circumvent the problem by using Server Options to change the shared memory size.
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
____________________________________________________________________________________
Note:
The value must be in hexadecimal. The new value won't take effect until you restart the X Server.
____________________________________________________________________________________
Graphics Administration Guide for HP-UX 10.20
Page 40