Parameter Info Block (PIB)
   Name            Size    Meaning
   buffer_size     32-bit  Size of the destination buffer, excluding
                           Copy segments.
   
      The total number of bytes in all of the segments that require a
      buffer to be created in the destination address space, with each
      buffer individually rounded up to an 8-byte alignment.  This is
      specified so that the kernel can allocate one large buffer for all
      segments before traversing the segment list.  When returning from
      a method, the buffer size only includes buffers allocated by the
      caller; "inout" segments where the caller specified a non-NULL
      ptr, and the callee did not increase the length, are not included
      (because the kernel does not need to allocate a caller-side buffer
      for them).  The kernel may throw an exception if the actual size
      is greater than specified in this field.
      
      This only covers the "normal" segments which are mapped only
      for the duration of the call.  Copy segments are handled
      separately.
   
   copy_size       32-bit  Size of all Copy segments.
   
      This is like buffer_size, but for Copy segments.

   objlist_ptr     pointer Pointer to the object list
	newobj_ptr      pointer Pointer to the new object list.
   objlist_len     32-bit  Length of the object list, in IDs
	newobj_len      32-bit  Length of the new object list.

      The object list is a special segment that contains object IDs
      rather than arbitrary data.  Each object ID will be translated
      into the destination ID-space, allocating new IDs when
      necessary.  The IDs themselves are 32 bits each, unsigned,
      regardless of the pointer size.  The first object in the list
      is the object to receive the message.

		Objects which live in this address space have the high bit
		clear; remote objects have the high bit set.  When sending
		an object reference that has not been exposed to the kernel
		before, its interface hash should exist in the newobj list.

		

   num_segments    32-bit  Number of data segments

   segment.ptr     pointer Pointer to data segment
   segment.len     32-bit  Length of data segment in bytes
   segment.flags   32-bit  Attributes of data segment
   reserved                Reserved for future use, and for
                           power-of-two indexing -- pad to
                           32 bytes.
   
      Each segment describes data being transmitted to and/or from the
      callee.  For out segments, the caller may designate a buffer to hold
      the data, or it may leave the ptr field NULL.  The caller may
      replace an out segment pointer with its own (it must do this if it
      was NULL), and it may change the length of the segment.  Except when
      flags such as Push or Shared force the kernel to map, rather than
      copy, the data, it will choose which method to use based on the
      size, page-alignment, and overmap status of the segment.

Segment Flags (see doc/orb/memory-management for more details):
   In            0x01    Data is copied/mapped from caller to callee.
   Out           0x02    Data is copied/mapped from callee to caller.
                         The data is unmapped from the callee unless
                         Copy is set.
   Inline        0x04    The callee cannot change the length of an
                         Out segment, and the caller must provide the
                         buffer.  Ignored for In segments.
   Copy          0x08    The segment is permanently copied into the
                         destination address space, with read/write
                         access.