Re: Wireshark memory handling

[Guy Harris <guy () alum mit edu>]

On Oct 5, 2009, at 11:46 AM, Jeff Morriss wrote:

> It's been a while, but my memory says that while memory-mapped files  
> are
> great, *growing* memory mapped files was (significantly) less  
> pleasant.

Growing a memory-mapped file *and keeping the entire file mapped into  
a single contiguous area* isn't very pleasant.

If you don't have to keep the entire file mapped contiguously, it's  
much easier - ftruncate() to grow the file, and another mmap() call to  
map the new area on UN*X, probably similar calls on Windows.

Using a mapped file as backing store for memory allocations shouldn't  
require a single contiguous area.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe