On 9/27/07, Rob van der Heij <[EMAIL PROTECTED]> wrote: My apologies. I just got a note saying it does not work. That comes from giving a recipe without trying to cook it ;-)
I overlooked the zero page and friends... So here's the revised list You determine them as follows in the System.map: 1. The 0 for the zero page 2. page of the last entry before _stext EW 3. page number of _stext (typically 0x000010000, so page 100 in hex) 4. last used page before _eshared (see note) SR 5. page number of _eshared (will be at start of segment, typically 400 hex) 6. last page before __bss_start EW > The pages between #2 and #3 and between #4 and #5 are not used. If you round > #2 and #4 up to the end of the segment, it means that those extra pages are > still saved in the NSS, but that's about all. So if you need the lazy approach, you only need to find #5 (it's on a segment boundary so will not change very often). The extra cost is probably not high, and you can only measure with the proper performance monitor ;-) Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
