> bss storage is represented in the executable image as simply a base
> address and a length - the loader (or image activator or whatever) simply
> creates the virtual memory of the correct size (and may zero it
> automatically). "data" storage requires that every byte of the memory
> layout be represented in the executable - this can lead to very large
> executables and longer image activation times.
Then what is the *advantage* of "data" storage? Does it result in
more efficient memory access? Does bss memory access require TLB
lookup? If so, could one place arrays in data rather than bss as a
means of alleviating TLB thrashing problems?
___________________________________________________________
Doug Sondak Boston University
email: [log in to unmask] Office of Information Technology
phone: (617)353-8273 111 Cummington Street
fax : (617)353-6260 Boston, MA 02215
|