Re: Performer allocating texture mem

New Message Reply Date view Thread view Subject view Author view

Fischler (src++at++rose)
Tue, 30 May 1995 15:36:30 -0700

+>---- On May 30, 2:45pm, David Luebke wrote:
> Subject: Performer allocating texture mem
->What mechanism does Performer use to allocate texture memory? We have RM5s
->and a flt database with a lot of textures, but after loading about 12 megs it
->freezes up. My theory is that the texture memory is getting fragmented (most of
->our textures are really small, 16x16 or smaller) and that the loader is
->going into a loop looking for a large enough chunk of memory to fit that next
->texture. Is this plausible? If so what do I do about it?

HW texture memory is allocated by the OS upon a pfApplyTex().
This probably first happens when you do a pfuDownloadTexList()
after reading in your database.
When does the freeze happen? In the loader before pfuDownloadTexList()
is called or after?
If you think that textures have been downloaded, you can
run osview and see if we are hung in the kernel or in user code.

src.

-- 
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++
Sharon Rose Clay (Fischler) - Silicon Graphics, Advanced Graphics Dev.
src++at++sgi.com  (415) 390 - 1002  FAX: (415) 965 - 2658  MS 8U-590
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++

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:51:32 PDT

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