b...@softjar.se (Johnny Billquist) writes:
>I don't see any realistic way of doing anything with that.
>It's basically the first process that tries to allocate another page
>when there are no more. There are no other processes at that moment in
>time that have the problem, so why should any of
>> > I have a program that keeps malloc()ing (and scribbling a bit
>> > into the allocated memory) until malloc() fails. The
>> > intention is to put pressure on the VM system to find out how
>> > much pool cache memory it can reclaim.
>> Such a program would be a prime
On Tue, Jun 14, 2022 at 07:59:33PM +0200, Johnny Billquist wrote:
> > What might be interesting is a way to influence the order in which
> > processes are chosen to kill...
>
> I don't see any realistic way of doing anything with that.
> It's basically the first process that tries to
>> > I have a program that keeps malloc()ing (and scribbling a bit
>> > into the allocated memory) until malloc() fails. The
>> > intention is to put pressure on the VM system to find out how
>> > much pool cache memory it can reclaim.
>> Such a program would be a prime
hello. Is this something madvise(2) could be extended to do?
-thanks
-Brian
On Jun 14, 2:47pm, Mouse wrote:
} Subject: Re: killed: out of swap
} >> What might be interesting is a way to influence the order in which
} >> processes are chosen to kill...
} > I don't see any realistic way
On 2022-06-14 20:47, Mouse wrote:
What might be interesting is a way to influence the order in which
processes are chosen to kill...
I don't see any realistic way of doing anything with that. It's
basically the first process that tries to allocate another page when
there are no more. There
>> What might be interesting is a way to influence the order in which
>> processes are chosen to kill...
> I don't see any realistic way of doing anything with that. It's
> basically the first process that tries to allocate another page when
> there are no more. There are no other processes at
On 2022-06-14 19:57, David Brownlee wrote:
On Tue, 14 Jun 2022 at 13:33, Robert Elz wrote:
NetBSD implements overcommitted swap - many processes malloc()
(or mmap() which that really becomes in the current implementation)
far more memory than they're ever going to actually use. It is only
On Tue, 14 Jun 2022 at 13:33, Robert Elz wrote:
>
> NetBSD implements overcommitted swap - many processes malloc()
> (or mmap() which that really becomes in the current implementation)
> far more memory than they're ever going to actually use. It is only
> when some real physical memory is
> I assume my impression is completely wrong (today).
OK, thanks for all the explanations and insights.
NetBSD implements overcommitted swap - many processes malloc()
(or mmap() which that really becomes in the current implementation)
far more memory than they're ever going to actually use. It is only
when some real physical memory is required (rather than simply a marker
"zero filled page might be
> I have a program that keeps malloc()ing (and scribbling a bit into
> the allocated memory) until malloc() fails. The intention is to put
> pressure on the VM system to find out how much pool cache memory it
> can reclaim.
> When I run that program (with swap space unconfigured), it doesn't
>
On 2022-06-14 12:59, Edgar Fuß wrote:
So what should the kernel do?
I don't know how thigs work under the hood today (I might have partially
known in the times of sbrk()), but I would suppose that malloc() will
ultimatively result in some system call enlarging the heap/data
segment/whatever.
> So what should the kernel do?
I don't know how thigs work under the hood today (I might have partially
known in the times of sbrk()), but I would suppose that malloc() will
ultimatively result in some system call enlarging the heap/data
segment/whatever. That system call could simply fail.
I
It's not the malloc that fails. It's the vm system trying to get a page
for you. At which point it might not be your process that is trying to
get a page when there are none free... So what should the kernel do?
Johnny
On 2022-06-14 12:01, Edgar Fuß wrote:
I have a program that keeps
I have a program that keeps malloc()ing (and scribbling a bit into the
allocated memory) until malloc() fails. The intention is to put pressure
on the VM system to find out how much pool cache memory it can reclaim.
When I run that program (with swap space unconfigured), it doesn't terminate
16 matches
Mail list logo
