"Jonathan A. Kollasch" writes:
> All too old, need the Unrestricted Guest feature on Intel for nvmm.
I updated the man page.
g...@lexort.com (Greg Troxel) writes:
>mlel...@serpens.de (Michael van Elst) writes:
>> t...@netbsd.org (Tobias Nygren) writes:
>>
>>>There exists ZFS code which hooks into UVM to drain memory -- but part
>>>of it is ifdef __i386 for some reason. See arc_kmem_reap_now().
>>
>> That's an extra
mlel...@serpens.de (Michael van Elst) writes:
> t...@netbsd.org (Tobias Nygren) writes:
>
>>There exists ZFS code which hooks into UVM to drain memory -- but part
>>of it is ifdef __i386 for some reason. See arc_kmem_reap_now().
>
> That's an extra for 32bit systems (later code replaced __i386
tlaro...@polynum.com writes:
> On Sat, Jul 29, 2023 at 12:42:13PM +0200, Tobias Nygren wrote:
>> On Fri, 28 Jul 2023 20:04:56 -0400
>> Greg Troxel wrote:
>>
>> > The upstream code tries to find a min/target/max under the assumption
>> > that there is a mechanism to free memory under pressure --
t...@netbsd.org (Tobias Nygren) writes:
>There exists ZFS code which hooks into UVM to drain memory -- but part
>of it is ifdef __i386 for some reason. See arc_kmem_reap_now().
That's an extra for 32bit systems (later code replaced __i386 with
the proper macro) where kernel address space is much
On Sat, Jul 29, 2023 at 12:42:13PM +0200, Tobias Nygren wrote:
> On Fri, 28 Jul 2023 20:04:56 -0400
> Greg Troxel wrote:
>
> > The upstream code tries to find a min/target/max under the assumption
> > that there is a mechanism to free memory under pressure -- which there
> > is not.
>
> There
On Fri, 28 Jul 2023 20:04:56 -0400
Greg Troxel wrote:
> The upstream code tries to find a min/target/max under the assumption
> that there is a mechanism to free memory under pressure -- which there
> is not.
There exists ZFS code which hooks into UVM to drain memory -- but part
of it is ifdef
