DragonFly BSD
DragonFly users List (threaded) for 2010-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: linux syscall madvise


From: Alex Hornung <ahornung@xxxxxxxxx>
Date: Tue, 5 Jan 2010 13:56:43 -0400

madvise is of no real relevance and is normally not a big deal either.
Implementing an empty dummy function will work perfectly fine as it
isn't required to do anything.

Cheers,
Alex Hornung

2010/1/4 Pierre Abbat <phma@phma.optus.nu>:
> I haven't managed to get ltp running, but I have run some Linux programs. I
> get this message in dmesg:
>
> linux: syscall madvise is obsoleted or not implemented
>
> This call is used to tell the kernel what the program plans to do with a
> region of memory. Values used in Linux but not BSD, according to the man
> pages, are:
> MADV_REMOVE: seems to mean the same as MADV_FREE
> MADV_DONTFORK: when fork() is next called, the child will not inherit the
> memory
> MADV_DOFORK: opposite of MADV_DONTFORK
>
> Pierre
> --
> li ze te'a ci vu'u ci bi'e te'a mu du
> li ci su'i ze te'a mu bi'e vu'u ci
>



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]