guile-devel
[Top][All Lists]
Advanced

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

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


From: tomas
Subject: Re: [PATCH] On Hurd, don't use not implemented madvise()
Date: Fri, 2 Jun 2017 10:39:51 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Jun 01, 2017 at 07:29:03PM -0400, Mark H Weaver wrote:
> Manolis Ragkousis <address@hidden> writes:

[...]

> > Also from my understanding not using madvise() ends up in slower
> > performance but it doesn't create problems to the program, right?
> 
> Some programs for Guile 2.2 may take advantage of the dynamically
> expandable stacks, because it allows programs to written in a more
> natural way.  Such programs may in some cases temporarily allocate a lot
> of stack space.  If this memory can never be reclaimed on Hurd, that may
> cause problems for some programs.

This would at least suggest having a way to query whether madvise is
available, through some introspection (giving the program a chance
to adapt its behavior)?

Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkxJFYACgkQBcgs9XrR2kbyNgCeJPtTvHeBJhIgiDHcIfip7aWt
e9kAn3fMsRpzS99+e0szQ7cuGo+X8Q/K
=9/ui
-----END PGP SIGNATURE-----



reply via email to

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