[Top][All Lists]

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

Re: [PATCH] On Hurd, don't use not implemented madvise()

From: Manolis Ragkousis
Subject: Re: [PATCH] On Hurd, don't use not implemented madvise()
Date: Thu, 1 Jun 2017 19:27:27 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

Hello Mark :)

On 05/30/2017 10:41 PM, Mark H Weaver wrote:
> Is there a test we could perform at run-time to discover whether
> madvise() is implemented?  If so, that would be greatly preferable.
Well madvise() on Hurd is a glibc no-op that fails with errno = ENOSYS.
Maybe I could allow madvise to run once and if it fails set a global
static variable called madvise_implemented to 0 (by default 1) and use
this to stop it from running again. WDYT?

Also from my understanding not using madvise() ends up in slower
performance but it doesn't create problems to the program, right?
Because in this case, it stills compiles guile, the problem is that it
continuously spams "madvise failed: Function not implemented". I could
make it not print it when errno = ENOSYS. WDYT?

Thank you,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]