Lines Matching full:small
100 code should distinguish "small" objects (kept in near data space) from
185 It also permits a small reduction in file size, because the compressor can
601 choice costs only a small amount of memory and has several benefits:
773 1. "Small" objects. Typically these require no more than 10K-20K total.
775 image size. Semantically they behave the same as small objects, but we
778 small objects by NEAR pointers.
779 * Pool allocation heuristics may differ for large and small objects.
789 objects for the data proper and small objects for the row pointers. For
791 these structures. Similarly, virtual arrays include a small control block
797 multiple passes through the image.) We also expect that only "small" objects
803 (For small images, the buffers might fit entirely in memory, so blind
812 (We don't bother to factor in the space needed for small objects, on the
824 Small objects of any lifespan may be allocated at any time. We expect that
825 the total space used for small objects will be small enough to be negligible
831 virtual-array access protocol is very small when no swapping occurs.
