On Fri, 15 Oct 2010 13:47:45 +0100 (BST), Salvatore Lionetti
<[email protected]> wrote:
> Hi,
> 
> I suggest you to use file with mmap.

only in well specified, bound and controlled situations.
mmap is known to shoot you in the back, as one of your link shows.
One app i tested a while back was designed with/around mmap
to read a database. They did not "plan" that the database
would grow above 1.5G and exhaust all the addressable RAM...
because of this the app crashed a lot :-(

and as the 3rd link shows, shared mem is taken in sandwich between
the heap and the stack so if you allocate a big file, you exhaust
both :-/

> I've used a lot in other projects, for example a 'qemulated' ppc405
based
> board interacting with extern management gui, or a 'soft real time'
> filtering of signal with stackable filter.
interesting :-)

yg

_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to