On Thu, Jul 11, 2019 at 05:26:34PM +, David Holland wrote:
> In practice (across arbitrary platforms) I wouldn't count on malloc
> necessarily respecting any of these limits,
Indeed, which was probably a large reason why this code is trying to find out
how much memory it should use. In our at
On Wed, Jul 10, 2019 at 05:59:05AM +, David Holland wrote:
> On Tue, Jul 09, 2019 at 10:24:53AM -0700, Graham Percival wrote:
> > RLIMIT_DATA
> > This is the maximum size of a data segment of the process, in bytes. If
> > this limit is exceeded, the malloc(
On Tue, Jul 09, 2019 at 07:17:39AM +0200, Martin Husemann wrote:
> The classical "data segment" (limited by RLIMIT_DATA) is not used much
> nowadays in NetBSD. Especially malloc() does not use it.
>
> RLIMIT_DATA The maximum size (in bytes) of the data segment for a
>
is helpful, this arose while testing the scrypt
1.2.99 pre-release. Scrypt attempts to use getrlimit(RLIMIT_DATA, ...) to
find out how much memory is available for encryption or decryption.
http://www.tarsnap.com/scrypt.html
Cheers,
- Graham Percival
#include
#include
#include
static void
the scrypt
1.2.99 pre-release. Scrypt attempts to use getrlimit(RLIMIT_DATA, ...) to
find out how much memory is available for encryption or decryption.
http://www.tarsnap.com/scrypt.html
Cheers,
- Graham Percival
