> It is. The pageout daemon initializes max_wired with:
>
> /* XXX does not really belong here */
> if (vm_page_max_wired == 0)
> vm_page_max_wired = cnt.v_free_count / 3;
>
I installed the following:
diff -r1.1 vm_pageout.c
1421c1421,1425
< vm_pag
> > vm.max_wired looks like a sysctl, but sysctl doesn't know about it.
> > sysctl: unknown oid 'vm.max_wired'
>
> Yes, indeed. I posted before looking at the diffs between RELENG_7 and
> CURRENT. The sysctl is only present in 8.0-CURRENT:
This is 7.0-RELEASE amd64 with 2 GiB of memory.
> Can
On Sat, 12 Apr 2008 23:55:49 +0200, Mel <[EMAIL PROTECTED]> wrote:
> As for the sysctl, I'm pretty sure it's a loader tunable, like the
> more known kern.maxdsiz.
It is. The pageout daemon initializes max_wired with:
/* XXX does not really belong here */
if (vm_page_max_wired ==
On Sat, 12 Apr 2008 13:51:16 +0100, Dieter <[EMAIL PROTECTED]> wrote:
>> > I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
>> > get mlock(2) failed: Resource temporarily unavailable.
>>
>> That's error EAGAIN:
>>
>> [EAGAIN] Locking the indicated range would exceed
>>
On Saturday 12 April 2008 14:51:16 Dieter wrote:
> > > I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
> > > get mlock(2) failed: Resource temporarily unavailable.
> >
> > That's error EAGAIN:
> >
> > [EAGAIN] Locking the indicated range would exceed
> >
> > I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
> > get mlock(2) failed: Resource temporarily unavailable.
>
> That's error EAGAIN:
>
> [EAGAIN] Locking the indicated range would exceed
> either the system or per-process limit
>
On Sat, 12 Apr 2008 08:15:41 +0100,
Dieter <[EMAIL PROTECTED]> wrote:
> I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
> get mlock(2) failed: Resource temporarily unavailable.
That's error EAGAIN:
[EAGAIN] Locking the indicated range would exceed
I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
get mlock(2) failed: Resource temporarily unavailable.
I commented out a ton of drivers in the kernel config file,
which I didn't do in 6.2, so the 7.0 kernel should be using less
memory, unless something still in there gained a lot of bloa
