Re: More pfDataPool

New Message Reply Date view Thread view Subject view Author view

Jim Helman (jimh++at++surreal)
Wed, 16 Nov 94 11:45:25 -0800

The problem is that pfDataPools must reside at the same space in
every process (see usinit(1)). This means that pfNewDPool should be
called in the larger process and pfAttachDPool should be called as
early as possible in the smaller process. It's OK to make calls like
pfNotifyLevel and pfAttachDPool before pfInit(). Errno 16 (EBUSY)
indicates a memory conflict.

In the next release, this error will print out:

Performer Warning (16): pfAttchDPool: could not map datapool /usr/tmp/dataPool.pfdpool into required address.
Try calling pfAttachDPool earlier in the application.

We'll probably do something different with data pools and addresses
in the next release. For now, you can call usconfig with
CONF_ATTACHADDR, to specify an allocation address out in the boonies
of addressland. Just be sure to set it back to ~0 after the call to
pfNewDPool. My choice for an address would be something just below
the stack, say between 0x7f000000 and 0x7ff00000.

rgds,

-jim helman

jimh++at++surreal.asd.sgi.com
415/390-1151

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:40 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.