what would happen if all sfio read-only opens that ended up using
mmap() used this flag? i.e., would there be a negative impact on
the system if everyone did this?
the reason is, at the sfio level the only current data flavor difference
is O_BINARY vs O_TEXT to placate DOS text; burying MAP_TEXT below the
sfio api would be good
On Wed, 20 Jun 2012 07:26:39 +0200 =?KOI8-R?B?z8zYx8Egy9LZ1sHOz9fTy8HR?= wrote:
> Glenn, would you think that using MAP_TEXT to map ksh93 script code
> via sfio would be a worth optimisation? We know that some customers
> have scripts larger than 100MB, and using large pages as implied in
> the text below might be good:
> mmap(2) on Solaris says:
> The MAP_TEXT option informs the system that the mapped
> region will be used primarily for executing instructions.
> This information can help the system better utilize MMU
> resources on some platforms. This flag is always passed by
> the dynamic linker when it maps text segments of shared
> objects. When the MAP_TEXT option is used for regular file
> mappings on some platforms, the system can choose a mapping
> size larger than the page size returned by sysconf(3C). The
> specific page sizes that are used depend on the platform and
> the alignment of the addr and len arguments. Several dif-
> frent mapping sizes can be used to map the region with
> larger page sizes used in the parts of the region that meet
> alignment and size requirements for those page sizes.
> Olga
> --
> , _ _ ,
> { \/`o;====- Olga Kryzhanovska -====;o`\/ }
> .----'-/`-/ [email protected] \-`\-'----.
> `'-..-| / http://twitter.com/fleyta \ |-..-'`
> /\/\ Solaris/BSD//C/C++ programmer /\/\
> `--` `--`
> _______________________________________________
> ast-developers mailing list
> [email protected]
> https://mailman.research.att.com/mailman/listinfo/ast-developers
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
