Re: valid VMA ranges and mincore()

2006-06-14 Thread Bruno Haible
Hello Konstantin, > > - Filling in values of -1 into the array could be done more easily by > > changing the statements in sys/vm/vm_mmap.c lines 861 and 902. > I do not agree. It zeroes array not only for holes, but also for (some) > skipped vm areas. ok, you understand the code better than I

Re: valid VMA ranges and mincore()

2006-06-14 Thread Konstantin Belousov
On Wed, Jun 14, 2006 at 02:04:08PM +0200, Bruno Haible wrote: > Hello Konstantin, > > Thanks for reacting on this issue. > > > Please, evaluate the patch. If it does what you need > > - It doesn't change the manual page mincore.2. Yes, it was intended. Exactly because I anticipated issues you de

Re: valid VMA ranges and mincore()

2006-06-14 Thread Bruno Haible
Hello Konstantin, Thanks for reacting on this issue. > Please, evaluate the patch. If it does what you need - It doesn't change the manual page mincore.2. - For unmapped areas, it appears to be filling in values of -1 into the array. This is not what Linux, Solaris, NetBSD do: They return -1

Re: valid VMA ranges and mincore()

2006-06-14 Thread Konstantin Belousov
On Sat, Jun 10, 2006 at 06:22:46PM +0200, Bruno Haible wrote: > Proposal 1: Change mincore() to behave like the one on NetBSD, Linux, > Solaris. Please, evaluate the patch. If it does what you need, I will push it for review. Index: vm_mmap.c ==

valid VMA ranges and mincore()

2006-06-10 Thread Bruno Haible
Hi memory management hackers, The mincore(2) system call is, on FreeBSD, not usable for some purposes for which it can be used on other platforms. Let me explain the purpose, the problem and two proposed solutions. The purpose === The task at hand is to enumerate the VMAs of the current